Google Play closed testing: the 12 testers, 14 days rule explained
By Test4Test · Updated
Quick answer
If your Google Play developer account is a personal account created after November 13, 2023, you must run a closed test with at least 12 opted-in testers for at least 14 consecutive days before you can apply for production access. Google reduced the number from 20 to 12 in December 2024. After the 14 days you apply in Play Console, answer questions about your test, and Google reviews the application.
Key facts
- Applies to
- Personal accounts since Nov 13, 2023
- Minimum testers
- 12 (was 20)
- Minimum duration
- 14 consecutive days
- Track type
- Closed testing
- Next step
- Apply for production access
Who has to meet the closed testing requirement?
The rule applies to personal developer accounts created after November 13, 2023. Organization accounts are exempt. If your account is older, or you publish under an organization, you can go straight to production.
Each new app on an affected account needs its own closed test before its first production release.
How to set up a closed test that counts
- 1
Create a closed testing track
In Play Console go to Test and release → Testing → Closed testing and create a track.
- 2
Upload a release
Upload your Android App Bundle to the track and roll it out to testers.
- 3
Add testers
Add testers by email list or Google Group. A Google Group, such as the Test4Test community group, lets many testers opt in with one address.
- 4
Share the opt-in link
Testers must open the opt-in URL and join the test, then install the app from Google Play.
- 5
Keep 12+ testers opted in for 14 days
Track your opted-in count in Play Console. If it drops below 12, the 14 days may not count.
- 6
Apply for production access
On the Dashboard, choose Apply for production and answer the questions about your test.
What Google asks when you apply for production
The application is a short questionnaire about how your test went. Expect questions along these lines:
- How did you recruit testers for your app?
- How easy was it to recruit testers, and how engaged were they?
- What feedback did you get and how did you act on it?
- Who is the intended audience and how does the app provide value?
- What changes did you make to your app based on testing?
Common closed testing mistakes
- Recruiting exactly 12 testers, then dropping below the minimum when one leaves
- Testers who join but never install or open the app
- Using an open or internal test instead of a closed test
- Applying for production with no feedback or changes to describe
- Switching tracks partway through, which makes 14 continuous days harder to show
How Test4Test helps you pass
Test4Test listings target 20+ testers so you have a buffer above 12. Every tester uploads a dated screenshot each day, so engagement is documented, and the final survey collects ratings and bug reports you can describe in your production application.
Get your first testers today
Join 1,000+ Android developers testing each other's apps. Free with tokens you earn by testing.
Frequently asked questions
Is it 12 or 20 testers for Google Play?
+
It is 12. Google originally required 20 testers when the rule launched in November 2023 and lowered it to 12 in December 2024. The 14-day duration did not change.
Do the 14 days have to be consecutive?
+
Yes. Testers must stay opted in for at least 14 days in a row, so keep a buffer above 12 in case someone leaves.
Can I use internal testing instead of closed testing?
+
No. Only a closed testing track counts toward the requirement.
What happens if my production application is rejected?
+
Google tells you why. Usually you continue testing, collect more engagement and feedback, and apply again.