PlayStore12TesterFor personal developer accounts created after November 13, 2023, Google requires at least 12 testers continuously opted in to a closed test for at least 14 days before applying for production access. Completing the period does not automatically publish the app.
Read Google’s current official requirement
Start with the requirement in your own account
Account type and creation date matter. Use the state shown for your app in Play Console rather than applying a general guide to every account. Tester count, app quality and release readiness are different questions.
Separate joining a test from accessing the app
Check the email list or Google Group access, the Google account being used and the opt-in link together. Follow Google’s track setup instructions for the configuration.
Google Play testing track setup instructions
Keep your own testing record
The worksheet below is our preparation aid, not an official Google form or eligibility certificate. Fill it in with information from your own test.
| Field | Information to record |
|---|---|
| Account scope | Record the requirement displayed in your own Play Console. |
| Build | Record the app version used for testing. |
| Access | Check the testing link and the path to join. |
| Scenario | Write down the actions you asked testers to try. |
| Feedback | Record the reported issue and reproduction steps. |
| Change | Record the change you made and the new build. |
| Follow-up | Record what happened when the flow was tested again. |
How to choose testers
People close to your app’s intended audience can help reveal confusing flows. When working with friends, developer contacts or a service, discuss feedback and scope as well as participation. Do not equate a supplier’s promised timeline with Google’s approval decision.
Where automated QA fits
QA on repeatable flows can help identify issues to fix. A software agent count is not a count of opted-in closed testers. Plan for these needs separately and check which one a service actually covers.
Before applying
Google asks about testing feedback and changes made in response. Use your own records instead of copying prepared answers describing somebody else’s test.