Before a personal developer account created after November 13, 2023 can publish an app to production on Google Play, it must run a closed test with at least 12 testers opted in for 14 continuous days. This is Google quality gate for new accounts. Here is exactly how it works, who it applies to, and how to set it up.
Who this applies to
The requirement applies to personal developer accounts created after November 13, 2023. If your account is older than that, or it is an organization account, you are exempt. Everyone else has to pass the closed test before they can apply for production access. There is no way to opt out.
The two numbers that matter
12 testers. At least 12 unique testers must be opted in to your closed test. These are 12 distinct Google accounts that joined through your opt-in link and installed on a real device. Emulators, bots, and duplicate accounts do not count. Google originally required 20 and lowered it to 12 on December 11, 2024.
14 continuous days. Those 12 testers must have been opted in for the last 14 days continuously when you apply. Continuous is the key word. If a tester drops out mid-cycle, their time does not count, and falling below 12 breaks your window.
Google states the rule but not what it costs you in practice. We run closed tests, so we can show the part the documentation leaves out: how many testers are still there when the 14 days are up.
Based on 139 tester opt-ins across closed-test campaigns whose 14-day window has already closed. Campaigns still running are excluded, because counting them would understate completion rates rather than merely leave them incomplete.
This is the whole reason the requirement is hard. Recruiting 12 testers is a one-afternoon problem. Keeping 12 testers opted in for 14 unbroken days is a two-week problem, and it is the one that sends developers back to the start of the clock.
How to set up closed testing in Play Console
- In Play Console, open Testing, then Closed testing, and create or select a closed track.
- Under Testers, create an email list or connect a Google Group, then add your testers Google account emails.
- Choose your countries and regions for the test.
- Add a feedback URL or email so testers can reach you.
- Upload your AAB or APK to the track and send the release for review.
- Google reviews it, usually within about a day, though new accounts can take up to 3 days.
- Once approved, share the opt-in link. The 14-day clock starts once you have 12 testers opted in and staying in.
Internal vs closed vs open testing
Internal testing is for up to 100 trusted testers and is fast, but it does not satisfy the production requirement. Closed testing is the track that counts toward the 12-tester, 14-day rule. Open testing is public and anyone can join. For the production requirement, you specifically need closed testing.
The part Google does not help with
Google tells you the rule. It does not tell you where to find 12 real people who will stay opted in for two weeks. That is where most new devs stall. Friends forget, swap communities churn, and Fiverr opt-ins teach you nothing about your app. TestFi solves the finding-and-keeping problem with real testers who install your app, use it, record their screen, and stay opted in for the full 14 days, plus an AI-scored UX report at the end. You pass the requirement and you find out what is actually broken in your app during the same two weeks, for $1.99 to $3.99 per tester a la carte, or $39.99 flat for the complete 12-tester bundle with Day 7 and Day 14 tracking included.
Frequently asked questions
What is the official Google Play closed testing requirement for personal developer accounts?
Per Google's official Play Console policy, personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for the last 14 days before they can apply for production access. The official source is Google's own Play Console Help page on app testing requirements (support.google.com/googleplay/android-developer/answer/14151465). Everything in this guide is based on that policy as of 2026.
What is closed testing on Google Play?
A testing track where a limited set of testers you invite can install your pre-release app. Personal accounts created after November 13, 2023 must complete it before applying for production access.
How long does closed testing take?
A minimum of 14 continuous days with at least 12 opted-in testers, plus review time of roughly 1 to 3 days for the release itself.
Does internal testing count toward the requirement?
No. Only closed testing counts toward the 12-tester, 14-day production requirement.
What if my account was created before November 13, 2023?
The requirement does not apply to you, and it does not apply to organization accounts.