Testing guides / Requirements · Reviewed 23 September 2026
Google Play’s 12-testers requirement, explained.
Before you organise testers, check which requirements apply to your developer account and app.
The requirement in one minute
- Who: personal developer accounts created after 13 November 2023, where the Play Console Dashboard shows production access is not yet available.
- What: complete a closed test after completing app setup.
- Count and duration: at least 12 testers continuously opted in for the preceding 14 days when you apply.
- Next step: apply through Play Console and answer questions about the test, the app and production readiness.
Check the Dashboard for your own app before treating any guide as decisive. Meeting the test condition lets you apply; Google still reviews the application.
Who does the requirement apply to?
Google’s published guidance applies to personal developer accounts created after 13 November 2023. They must complete a closed test with at least 12 testers continuously opted in for 14 days before applying for production access.
Use your own Play Console dashboard as the starting point. Do not assume an older tutorial or another developer’s account has the same requirements.
Internal, closed, open or production?
| Track | Who can join | Where it appears | Counts toward the 12-testers / 14-days condition? | Best use |
|---|---|---|---|---|
| Internal | A small trusted group you choose | Not publicly discoverable | No | Catch install, sign-in and core-flow problems early |
| Closed | A controlled group using your tester list or configured access method | Share access directly with testers | Yes, for covered personal accounts | Run the required testing period and collect feedback |
| Open | Anyone who joins the programme | Visible on Google Play | No | Broader voluntary testing after production access is available |
| Production | Everyone | Visible on Google Play | Not applicable | Public release |
See Google’s track setup guide. Internal testing does not substitute for the required closed test.
Why do some guides mention 20 testers?
Older guidance and some provider packages use a 20-tester count. The current published minimum for affected personal accounts is 12. A provider may assign more people for its own coverage; use the current requirement shown for your account when checking eligibility.
What does continuous opt-in mean?
A tester needs to remain opted in for the required continuous period. Leaving and rejoining does not combine separate stretches into one qualifying period.
For your own planning, keep a simple record of invitations, opt-in checks and participation issues. A calendar reminder is useful, but it cannot verify eligibility in Play Console.
Official rule versus useful planning advice
| Google publishes | Practical planning advice |
|---|---|
| At least 12 testers must be opted in continuously for the preceding 14 days when you apply. | Recruit more people than the bare minimum when your plan allows, so a participation issue does not leave you with no options. |
| Google asks about tester engagement, feedback and production readiness. | Give testers a short task list, one feedback channel and a way to report problems clearly. |
| You must summarise testing feedback in the production-access application. | Keep a dated record of feedback, decisions, fixes and retest results from day one. |
The right column is project advice, not an extra Google requirement. Follow the Dashboard and Google’s current guidance if they differ from a blog or provider claim.
What happens after the test?
You apply for production access and answer questions about your test, feedback and readiness. Reaching the minimum count and duration is not automatic approval. Google can request more testing.
Read Google’s current requirements and production-access guidance for the full account-specific process.
Plan useful testing alongside the count
Our recommendation: list a handful of realistic tasks and give testers a clear feedback channel. Track problems that affect those tasks, then repeat the relevant checks after fixes. This makes the testing more useful to you and gives you real information for your application.
Don’t confuse paid coordination with a promise of approval. Before choosing support, ask who manages participation, what feedback you receive and how interruptions are handled.
Next steps
Ready to organise your closed test?
See what our Google Play closed-testing service includes, then compare packages and coverage for your app.
Get testersPrepare your production-access testing summary
Use a blank worksheet to organise actual engagement, feedback, changes and readiness notes.