Google Play's 12 testers rule: how to pass the closed test
Updated
Google requires new personal developer accounts (created after November 13, 2023) to run a closed test with at least 12 testers who stay opted in for the 14 days before applying for production access. Recruit more than 12 people, keep them enrolled for the full two weeks, and make sure they actually install and use the app.
What the rule says
Before your first app goes to production, your closed test must have at least 12 testers opted in for the last 14 days in a row. You then apply for production access from the Play Console and answer a few questions about the test.
How to find your 12 testers
- Friends, family and colleagues with an Android phone: aim for 15 to 20 so a few drop-outs don't hurt
- Your first customers or newsletter subscribers, who get early access in exchange
- A Google Group as the tester list: people join the group, and the group is added to the closed test
- Developer communities that swap testing with each other
Mistakes that cost you two more weeks
- Fewer than 12 people still opted in on the last day
- Testers who joined but never installed the app
- Paying for fake testers: it risks your developer account
- Vague answers in the production access form: explain what you tested and what you changed
Where Bappfy fits
Bappfy sends each build of your app to Google Play internal testing automatically, so you can share new versions with your testers during the 14 days without uploading anything by hand. See publishing a React Native app to Google Play.
Frequently asked questions
- Does the rule apply to every account?
- Google describes it for personal developer accounts created after November 13, 2023. Check the Play Console help page for your account type.
- Can testers be people I know?
- Yes. Anyone with a Google account who opts in to your closed test counts, as long as they stay opted in for the 14 days.