To set up a Google Play closed test, open your app in Play Console and go to Test and release > Testing > Closed testing. Choose an email list or Google Group for access, add a feedback contact, create and roll out a test release, then send testers the opt-in link. If your personal developer account was created after November 13, 2023, Google requires at least 12 testers to stay opted in continuously for at least 14 days before you can apply for production access.
Choose the testing track that fits your release
Google Play offers internal, closed, and open testing tracks. The main differences are who can join, when the track is useful, and whether production access is already available.
As an Amazon Associate I earn from qualifying purchases.
| Track | Who can join | When it fits | Production access |
|---|---|---|---|
| Internal | A small trusted group | Early checks; it can be used before full app setup is complete | Can be used before production access |
| Closed | Selected testers you control | Testing with a defined audience before wider release | Can be used before production access |
| Open | Anyone who can access the test | Broader testing | Available after production access |
For instructions on tracks and access, see Google’s guide to setting up an open, closed, or internal test. Internal testing is optional; it can help you check an early build with a small trusted group before setting up a closed test.
Before creating the closed test
Closed testing can start once the app setup is complete. If the release action is unavailable, check the app dashboard for tasks that still need attention. Google’s app dashboard guide explains the setup tasks and their status.
#1 Best Overall
You do not need to buy a separate Android device to run the campaign. Invite testers to use their own compatible devices; Google’s setup guidance does not list a developer-owned device as a requirement.
Set up the track and tester access
- Open the track. In Play Console, select your app and choose Test and release > Testing > Closed testing. Use the initial closed track, or create a separately named track if different groups need separate access or builds.
- Choose an access method. Manage testers with an email list or Google Groups. For a Google Groups test, testers must join the specified group before opting in. Google’s test setup instructions cover creating and selecting lists and adding group addresses.
- Add a feedback channel. Enter a feedback URL or email address; it appears on the opt-in page. Test versions cannot receive public Play reviews, so tell participants how to report bugs and usability problems. Closed and open testers can also send private feedback through Google Play.
Create a release and share the opt-in link
- Prepare a test release. Create a release on the closed-testing track and roll it out. Google’s release preparation and rollout guide explains the release workflow.
- Wait for the link if this is the first publication. Google says a test link may take several hours to become available after the first publication.
- Send the link directly. Share the Play Store URL or opt-in link with the intended testers. Before a public rollout, people 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.
Give testers a short brief describing what to try, how to report problems, and when you need feedback. Clear tasks help you gather useful observations rather than simply counting opt-ins.
Meet the production-access test requirement, if it applies
Google’s current guidance applies the 12-tester rule to personal developer accounts created after November 13, 2023. For those accounts, at least 12 testers must be opted in continuously for at least 14 days when the developer applies for production access. The requirement is stated as a tester count, not a number of physical devices. It refers to continuous opt-in, not keeping the app installed for the entire period. See Google’s requirements for new personal developer accounts.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsContinuity matters: if a tester opts out and later opts in again, the earlier days do not count toward a consecutive 14-day period. Keep track of participation during the test so you can address opt-outs before applying.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Apply for production access
When ready, open the Play Console Dashboard and select Apply for production. The application asks about the closed test, the app, and its readiness for production. Be prepared to describe:
- How testers engaged with the app and how you collected their feedback.
- What you changed in response to testing.
- Who the app is for and what value it provides.
- Why the app is ready for production.
Completing the minimum test period does not guarantee approval. Google evaluates the application and may require additional testing, as described in its production-access guidance.
Quick Recap
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.
