Guide · Updated 9 October 2026
Google Play closed testing checklist: 12 testers, 14 days
Everything a new Android developer needs to get through Google Play’s closed testing requirement and apply for production access, step by step.
The rule in one line: if your personal developer account was created after 13 November 2023, you must run a closed test with at least 12 testers who stay opted in for at least 14 days in a row before you can apply to publish to production.
This checklist is based on Google’s app testing requirements and on what we’ve learned running closed tests for our own games. Google’s rules can change, so always check Play Console for the latest wording.
1. Check whether the requirement applies to you
- Personal account created after 13 November 2023: yes, you need the 12-tester, 14-day closed test.
- Personal account created before that date, or an organisation account: this requirement doesn’t apply to you.
- Not sure? Play Console shows a closed testing requirement on your Dashboard if it applies.
2. Get your app ready before inviting anyone
- A signed release build (Android App Bundle) uploaded to a Closed testing track. Internal testing is optional and doesn’t count towards the requirement.
- A store listing with your app name, short and full description, icon, feature graphic and phone screenshots.
- The App content declarations: privacy policy, app access (add test login details if your app needs an account), ads, content rating, target audience, and data safety.
- The countries or regions your closed test is available in. Your testers must be in one of them.
- A testers list: an email list or a Google Group. A Google Group is easiest, because testers can join it themselves.
- Your opt-in link: in the closed testing track, open Testers and copy the “Join on the web” link.
3. Recruit more than 12 testers
- Aim for 15 to 20. Some people will drop out, and anyone who opts out before 14 days doesn’t count.
- Every tester must open the opt-in link, tap Become a tester, then install the app from Google Play using the same Google account that’s on their phone.
- Anyone who joins late starts their own 14 days, so recruit everyone before you start counting.
- Ask testers to stay opted in until you have been approved, not just for 14 days.
4. During the 14 days: make testing real
Google’s production access form asks how testers used your app and what feedback they gave, so installs alone aren’t enough.
- Give testers something to do each day: try a feature, finish a level, change a setting.
- Collect feedback somewhere you can quote it later: a form, email, or a Discord channel.
- Ship at least one update that fixes something testers reported, and note what you changed.
- Keep a simple log: what testers tried, what broke, and what you improved.
5. Apply for production access
- When the requirement is met, go to Dashboard in Play Console and click Apply for production.
- The form has three parts: your closed test (how you recruited testers, how they used the app, what feedback you got), your app (audience and what makes it useful), and your production readiness (what you changed and why you think it’s ready).
- Be specific. Real numbers and real examples of feedback work much better than general statements.
- Google says review usually takes seven days or less, but it can take longer.
6. If Google says you need more testing
- Keep your closed test running. Don’t remove your testers.
- Improve engagement: give testers clearer tasks, and ask them to use the app regularly.
- Release an update based on their feedback, then apply again with more detailed answers.
Common mistakes that cost developers weeks
- Starting with exactly 12 testers, then losing one on day 10.
- Testers who opt in but never install the app, or install it with a different Google account.
- Testers outside the countries selected for the closed test.
- Unfinished App content declarations, which can block review.
- Vague answers on the production form, like “testers liked the app”.
- Swapping ratings or reviews with other developers. It breaks Google Play policy and can put your account at risk.
Frequently asked questions
Only if you have a personal Google Play developer account created after 13 November 2023. Organisation accounts, and personal accounts created before that date, don’t need it. If it applies to you, Play Console shows the closed testing requirement on your Dashboard.
At least 12 testers who have been opted in to your closed test for the last 14 days in a row when you apply for production. Recruit 15 to 20, so a few drop-outs don’t cost you time.
Google only counts testers who have been opted in continuously for the last 14 days. A tester who opts out stops counting. A replacement, or someone who leaves and rejoins, starts their own 14 days from the day they join. If you drop below 12 testers with 14 unbroken days, you have to wait until you are back above 12.
Installing alone isn’t enough to get through review. Google’s production access form asks how testers used your app and what feedback they gave. Give testers a small task each day and keep a record of their feedback.
In Play Console, open Testing > Closed testing, choose your closed testing track, open the Testers tab and copy the “Join on the web” link. Menu names can change slightly, so look for Closed testing if you can’t see it.
Yes, and you should. Releasing an update that fixes something testers reported gives you a concrete example for the production access form. Upload it to the same closed testing track so your testers get it.
The usual reasons are testers who installed but didn’t really use the app, vague answers on the form, fewer than 12 testers with 14 unbroken days when you applied, or unfinished App content declarations. If Google says you need more testing, keep your test running, improve engagement, ship an update and apply again. Check the message in Play Console for the reason given for your account.
Yes. Each app needs its own closed test with its own 12 or more testers. In Tester Groups you can add several apps with /myapp, and each one goes into a different group, so a group never holds two apps from the same developer.
Join our Discord, run /join with the Google account you use on Google Play, then /myapp to add your app, its opt-in link and a few daily tasks. Groups of up to 16 developers start automatically when they’re full. Everyone installs every app in the group, then for 14 days does one small task per app each day and logs it with /checkin. Three missed days and you leave the group. At the end, every developer gets a feedback report for the production access form.
Yes, completely. Tester Groups is run by TheDogBowl, a small indie studio that needed testers too.
Need testers now? Read how Tester Groups work or join our Discord and run /join to get into the next group.
Need 12 testers? Join Tester Groups
Tester Groups is our free community where indie Android developers test each other’s apps properly: 14 days, a small task every day, and a feedback report at the end to help with the production access form.