What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To set up a Google Play closed testing campaign, open Test and release > Testing > Closed testing in Play Console, choose who may join, add a feedback contact, create and roll out a test release, then share the opt-in link with your testers. If your developer account is personal and was created after November 13, 2023, Google requires at least 12 testers to remain opted in continuously for at least 14 days before you can apply for production access. This is a tester opt-in requirement, not a requirement for 12 devices. Google Play Console Help
Choose the right Google Play testing track
Closed testing is for a selected group of testers. It lets you control access while collecting feedback before a broader release. The right track depends on how much control you need and where the app is in development.
| Track | Audience access | When it fits | Production access |
|---|---|---|---|
| Internal testing | A small trusted group | Early checks; it can be available before the rest of app setup is complete. | It is an optional early testing track. |
| Closed testing | Testers you select through email lists or Google Groups | Controlled testing with a defined group. | It can be used to meet the test requirement that applies to some new personal accounts. |
| Open testing | Anyone can join | Broader testing when you are ready to open participation. | Available after production access. |
Google describes these tracks in its testing-track guidance and its article on testing requirements for new personal developer accounts.
Set up the closed test in Play Console
1. Complete the app setup needed for a closed release
Closed testing can start once the app setup tasks required for the release are complete. If the option to create or roll out a release is unavailable, check the app dashboard for remaining setup tasks. Internal testing may be available sooner if you want to check a build with a small trusted group first. See Google’s guidance on setting up your app on the dashboard.
#1 Best Overall
2. Open or create a closed-testing track
Select your app, then go to Test and release > Testing > Closed testing. Use the initial closed track, or create a separately named track if different groups need distinct builds or access. Google’s test setup instructions explain the track options.
3. Choose how to manage testers
Use an email list or a Google Group to define who can opt in. You can create an email list and select it for a release, or enter the address of a Google Group. For a Google Groups test, testers must first join the specified group; only its members can then join the test.
4. Add a feedback contact
Enter a feedback URL or email address. It appears on the tester opt-in page, giving participants a direct way to report bugs and usability issues. Testers cannot post public Play reviews for test versions, although closed and open testers can provide private feedback through Google Play.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →5. Create and roll out a test release
Prepare a release on the closed-testing track and roll it out. Follow Google’s release preparation and rollout instructions. The first test link may take several hours to become available after the initial publication.
6. Send testers the link and instructions
Share the Play Store URL or the opt-in link directly. Before a public rollout, testers generally cannot find an internal or closed-test app by searching Google Play. The opt-in link appears only when the app status is Published, not Draft or Pending publication. Tell participants which features to try and how to send feedback.
Meet the production-access testing requirement, if it applies
Google’s requirement applies to personal developer accounts created after November 13, 2023. For those accounts, at least 12 testers must be opted into the closed test continuously for the 14 days immediately before applying for production access. The cited guidance counts opted-in testers; it does not specify 12 distinct devices or require testers to keep the app installed throughout the period. Google’s account-specific requirements
Continuous opt-in matters: if a tester opts out and later opts in again, their earlier days do not count toward a consecutive 14-day period. Track participation so you can see whether the required number remains opted in for the full window.
Free tools Windows power users keep installed
One-click scans. No signup required.
Apply for production access
When ready, open the Play Console Dashboard and select Apply for production. The application asks about your closed test, the app, and its readiness for production. Be prepared to describe tester engagement, how you collected feedback, what you changed in response, who the app serves and what it offers, and why you believe it is ready. Google may request more testing, and meeting the minimum test period does not guarantee approval. Google Play Console Help
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
