Google Play: 12 Testers for 14 Days

Everything you need to understand the closed-testing requirement for new personal developer accounts, how the 14-day window is counted, what happens when testers leave, and what you do after the test is complete.

Last reviewed: August 26, 2026 · Source: Google Play Console Help

What is the requirement?

If your Google Play developer account is a personal account created after November 13, 2023, your app must go through a qualifying closed test before you can apply for production access. Google's current requirement is at least 12 testers who have been opted in continuously for at least 14 days. citeturn977959search0

Meeting the count and duration is the gate for applying. It does not guarantee approval: Google also asks questions about your closed test, your app, and your production readiness. citeturn977959search0turn977959search3

Who does it apply to?

This requirement applies to personal Google Play developer accounts created after November 13, 2023. Google's help page describes separate testing workflows for internal, closed, open, and production tracks. citeturn977959search0

The requirement is not the same thing as a universal rule for every developer account or every testing track. Check the account and Play Console workflow that applies to your app before relying on the 12/14-day checklist.

What is a closed test?

Closed testing lets you distribute a pre-release version to a controlled group of testers. The test is managed through Play Console, and only people in the selected tester group can access that closed version. citeturn977959search1turn977959search7

Google distinguishes closed testing from internal testing, which is designed for a smaller trusted group, and open testing, where anyone can join after you have production access. citeturn977959search1

What does "12 testers" mean?

The relevant number is not simply the number of people you invited. Google says that, when you apply for production access, at least 12 testers must be opted in to your closed test continuously for the preceding 14 days. citeturn977959search0

That is why a buffer can be operationally useful even though Google's minimum is 12: losing one tester can take the qualifying count below the minimum.

Check your numbers with the 12 Tester Calculator →

What does "14 continuous days" mean?

Continuity matters. A tester who opts in, stays in the test for fewer than 14 days, and then opts out does not satisfy the continuous 14-day requirement. If that tester opts back in later, the qualifying 14 days must still be consecutive. citeturn423118search0turn977959search3

The cleanest way to think about the rule is that you need the qualifying group to remain continuously opted in through the period leading up to the production request—not simply reach 12 people once.

What happens if someone leaves?

If a tester opts out and you fall below 12 qualifying testers, you no longer have the required minimum at that point. A tester who later opts back in does not retroactively turn a broken continuous period into an uninterrupted one. citeturn423118search0

The practical response is to keep enough eligible testers in the programme that one dropout does not put the test below the minimum.

Do testers need to use the app?

The requirement itself is about continuous opt-in, but Google also evaluates tester engagement when reviewing a production-access request. Google asks developers to describe whether testers used the available features, whether usage matched expected production behaviour, and to summarize the feedback they received. citeturn977959search3

Google also recommends giving testers clear instructions on what to test, specifying the feedback you want, encouraging use of the app's features, and providing a clear feedback channel. citeturn423118search3

How to recruit testers

Google recommends using personal and professional networks, relevant communities, social channels, and testers who resemble your intended audience. It also recommends recruiting a diverse group so you can catch issues that may affect different users or device types. citeturn423118search3

For a managed service, the important thing is not just filling a list. You want people who can actually join the closed test, stay opted in, use the build, and provide useful findings.

See ClosedTest testing plans →

How to verify testers

In Play Console, set up the closed test and its tester access method, provide a feedback channel, and share the test or opt-in link with the testers. Google's setup instructions describe email lists and Google Groups as supported closed-testing access methods. citeturn977959search1

On the tester side, verify that they actually joined the test rather than merely receiving an invitation. For a practical operational check, maintain your own tester roster and evidence of check-ins and findings.

What happens after 14 days?

Once the closed-test requirement is satisfied, you can apply for production access from the Play Console Dashboard. The application asks questions about the closed test, your app, and your production readiness. citeturn977959search0turn977959search5

Reaching day 14 is therefore a milestone, not the end of the process. Before applying, make sure your answers accurately describe what happened during testing and what you changed based on what you learned.

Production access

In Play Console, use Dashboard → Apply for production after you meet the closed-testing criteria. Google's current application has sections covering the closed test, the app/game, and production readiness. citeturn977959search0turn977959search5

Google asks about tester engagement and feedback, then asks what you learned and what changes you made based on the closed test, plus how you determined the app was ready for production. citeturn977959search3

Why Google may request additional testing

Google says additional testing may be required after you apply. Reasons can include having fewer than 12 opted-in testers or insufficient tester engagement during the test period. citeturn423118search0turn423118search5

This is why a completed calendar window does not mean the production request is guaranteed to succeed. Keep testing, fix issues, and make sure your production request accurately reflects the actual test.

Common mistakes

FAQ

Primary source: Google Play Console Help — App testing requirements for new personal developer accounts. citeturn977959search0