Here are the details of google play testing requirements Google Play Store’s “14‑day closed testing / testing policy” (for new personal developer accounts), as of the latest updates.
🛠 What is it
-
- Google play testing requirements by Google Play for new personal (individual) developer accounts (i.e. developer accounts created after November 13, 2023).
-
- The goal is to ensure apps have some real user feedback and stability before being published to the public (Production).
✅ Key Requirements
-
- Closed Testing Track
You must use a closed test track (not internal, not open) in the Google Play Console.
- Closed Testing Track
-
- Minimum Testers
At least 12 testers must be opted‑in to the closed test. This was earlier 20 testers; Google reduced the number for new personal accounts.
- Minimum Testers
-
- Duration — “14 days”
The test must run for 14 consecutive days with those testers, during which they must remain opted in and keep the app installed.
- Duration — “14 days”
-
- Testers’ behavior / engagement
-
- Testers should not uninstall the app during these 14 days.
-
- It’s implied that the testers should be active (open/use the app), though the exact level of activity required is a bit unclear in the public policy.
-
- The app may be updated (new build / version) during these 14‑day period if needed. Updates don’t reset the entire 14‑day window.
-
- Testers’ behavior / engagement
-
- After testing — Production Access
Once you’ve met the closed testing requirements (testers + 14 days), you can apply for production access in the Play Console. Google will ask some questions about the closed test & the readiness of your app.
- After testing — Production Access
⚠ Exceptions / Who is NOT Required
-
- Developer accounts registered before November 13, 2023 are not subject to this policy.
-
- Organization (business) developer accounts are also not typically required to follow this closed testing mandate.
🔍 Common pitfalls to avoid
-
- Having fewer than 12 testers, or testers dropping out (uninstalling) during the 14 days. This can cause the requirement to fail.
-
- Testers not engaging / not using the app at all. Sometimes Google expects some usage, not just staying opted in.
-
- Tester opt‑ins being delayed (if testers join later than others, the 14‑day count starts only once the minimum number have opted in).
-
- Not setting up the closed testing track properly (wrong testers, region availability, missing invites) can delay or block progress.
- Failing to complete the follow‑up “production readiness” questionnaire / requirements after the test period.