Guide
Google Play Closed Testing Checklist (12 Testers, 14 Days)
Updated 27 September 2026
Quick answer
Upload a signed AAB to a closed testing track, add at least 12 testers (with a buffer), roll out the release, keep 12 or more testers opted in for 14 days in a row while you collect feedback and ship fixes, then apply for production access from the Dashboard and answer Google's questions about your test.
Before the test
- App content, privacy policy URL, data safety form and content rating completed in Play Console.
- A signed Android App Bundle (AAB) with the final package name.
- A closed testing track created, with the countries you want testers in.
- A tester list: a Google Group or email list with more than 12 people, so drop-outs do not break the count.
Starting the test
- 1Create a release on the closed track, upload the AAB and roll it out.
- 2Add the tester Google Group on the Testers tab (with 12Tester Community: get12testers@googlegroups.com) and save.
- 3Share the opt-in link; testers join, accept and install from the Play Store.
- 4Check the opted-in count in the Dashboard over the next 24-48 hours.
During the 14 days
- Check daily that 12 or more testers stay opted in.
- Collect feedback in one place (see our feedback template) and fix real issues.
- Ship updates to the same closed track; do not change the tester list.
- Write down what testers reported and what you changed.
Applying for production
- 1Open the Dashboard and use "Apply for production" once it unlocks.
- 2Describe how you recruited testers, how they used the app and what feedback they gave.
- 3Explain what you changed based on feedback and why the app is ready.
- 4Submit and wait for Google's review, which typically takes days, not hours.
Frequently asked questions
How many testers should I start with?
More than 12. A buffer of a few extra testers protects the 14-day count if someone leaves.
Can I use internal testing instead?
No. The production access requirement is met through a closed testing track.