Google Play Closed Testing Requirements. 12 Testers for 14 Continuous Days.
A complete breakdown of Google Play's 12 testers for 14 consecutive days policy, track configurations, feedback gathering, and how to successfully apply for production track access.
The Official Google Play Testing Rule
Based on official Google Play developer documentation for personal accounts.
Under Google Play developer policies, personal developer accounts created after November 13, 2023 must run a closed testing track meeting the following strict criteria before applying for Production access:
At least 12 individual testers opted into your closed testing track.
Read 12 Testers Guide ➔Testers must remain continuously opted-in for at least 14 consecutive days.
Read 14 Days Guide ➔Complete the mandatory 14-day survey before Google reviews your app for release.
Production Access Guide ➔Official Reference: Google Play Console Help — Set up an open, closed, or internal test.
How to Complete Google Play Closed Testing
A step-by-step roadmap to successfully finish testing and qualify for production access.
1. Configure Closed Track & Google Group
In Play Console, go to Testing > Closed testing, create a new track, and select Google Groups for tester access. Learn how in our Google Play testers setup guide.
2. Recruit 15 to 20 Android Testers
While Google requires 12, dropouts can reset your clock. Recruit 15-20 peer developers via Testers Hub to keep your active opt-in count well above the threshold.
3. Maintain Continuous 14-Day Cohort
Ensure testers keep the app installed for 14 continuous days. Review the detailed rules in our 14 days testing guide.
4. Collect Feedback & Push Iterations
Collect bug reports and crash telemetry from testers. Release at least one update during testing to demonstrate active maintenance to Google reviewers.
5. Apply for Production Track Access
Once the 14-day requirement is fulfilled, click Apply for production and answer the mandatory review questions. Follow our production access questionnaire guide.
Explore Closed Testing Guides
Detailed masterclasses covering every phase of your pre-launch testing lifecycle.
How to Find Real App Testers
Learn ethical strategies to recruit genuine Android testers via squads, peer communities, and Google Groups.
Read Finding Testers Guide ➔Why Google Rejects Testing
Diagnose common pitfalls including ghost dropouts, zero feedback submissions, and low engagement vitals.
Review Rejection Reasons ➔Production Questionnaire Guide
Prepare authentic, well-documented answers for the 14-day closed testing questionnaire in Play Console.
View Questionnaire Tips ➔Closed Testing FAQs
Common questions about meeting Google Play closed testing benchmarks.
For personal developer accounts created after November 13, 2023, Google requires developers to run a closed test with at least 12 testers opted in continuously for at least 14 consecutive days before applying for production access.
To complete closed testing, create a closed track in Play Console, configure a Google Group feedback channel, recruit 15-20 active Android testers, maintain 12+ opted-in participants for 14 continuous days, collect bug feedback, and complete the Production Access questionnaire.
You can find testers by joining reciprocal developer communities like Testers Hub, posting your Google Group in Android closed testing developer hubs (e.g. Reddit r/AndroidClosedTesting), or using managed testing cohorts.
If the count of active opted-in testers drops below 12, Google's 14-day tracking clock may pause or reset. Developers typically maintain 15-20 testers to ensure a safe margin.
Yes. Google Play allows closed testing tracks to be shared via Google Groups email lists, which simplifies adding multiple testers without manually entering individual email addresses.