A continuous testing period
Google specifies a continuous period during which testers must stay opted in. The widely quoted requirement is 14 continuous days, and continuity is the detail that decides whether you meet it.
Google Play Closed Testing Requirements
Eligibility, tester participation, testing duration and application review: what Google expects, and how to check the current rules for your own account type.
Which accounts the testing prerequisite applies to
Personal and organisation accounts are treated differently
The closed testing prerequisite for production access has applied to personal developer accounts created after Google introduced the rule. Organisation accounts have generally been treated differently, and there are verification requirements attached to organisation accounts that change the picture.
Because the eligibility rules are policy rather than product behaviour, the only reliable answer is the one Google publishes for your account type and creation date. Check that before you plan anything.
What else has to be in place
- The app must be published to a testing track and installable by your testers.
- Developer account verification must be complete for the account type you hold.
- The app must comply with Play policies. Testing does not exempt an app from review requirements.
- Store listing details must be accurate. Production review considers the listing as well as the build.
Tester participation
A minimum number of opted-in testers
Google asks for a minimum number of testers who are actually opted in to your closed test. The commonly cited figure is 12. It is a threshold on opted-in testers, which is why invitation counts do not satisfy it.
- Each tester opts in with a Google account, and one account fills one slot.
- Duplicate or incorrect addresses reduce the real count without reducing the apparent count.
- Testers must remain opted in, not merely opt in once and leave the track.
- Paid testers are acceptable to Google provided they are real accounts genuinely installing and using the build.
What developers most often get wrong
- Reporting the number of invitations sent rather than the number of testers opted in.
- Not recording opt-in dates, which makes the continuous period impossible to state accurately.
- Losing testers part-way through the window and not noticing until the application.
- Assuming internal testers count towards a closed testing requirement. Confirm which track satisfies the rule for your account.
Testing duration and application review
Interruptions matter
If the opted-in tester count drops below the threshold during the window, or a tester leaves and rejoins, the continuous run you are relying on can be broken. Monitoring during the window is how you avoid finding out afterwards.
Review considers more than the test
The application is reviewed alongside the app itself and your store listing. Testing organised perfectly around an app that is not ready for release will not carry the application.
Accuracy is the point
The information you submit about your testing should describe what actually happened. Inconsistencies between the form and the reality of the campaign are avoidable only if the campaign was recorded as it ran.
Understanding an unsuccessful application
Reasons vary, so read the message you receive
Unsuccessful production access applications do not all fail for the same reason, and the reason given to you is the only authoritative explanation of your case. Attempting to diagnose it from other developers' accounts of their own rejections usually leads to fixing the wrong thing.
What you can control is whether the testing part of your application is defensible. If the decision cited testing, the useful questions are whether the opted-in tester count genuinely met the threshold, whether the period was continuous, and whether the information submitted matched what happened.
- Check the opted-in count, not the invite count, for the whole window.
- Check the period for gaps caused by testers leaving or rejoining.
- Check that your app is genuinely release-ready, separately from the testing question.
- Check that the details submitted about the app and its testing are consistent with the listing and the console.
Questions about the requirements
Run a Campaign That Meets the Bar
We will set the campaign up around the current requirements for your account: the right tester count, tracked opt-ins and a continuous window you can state precisely.
Policy content reviewed 2026-09-27. Always confirm current requirements with Google.