Google Play's 12 testers, 14 days requirement, explained.
If you opened a personal Google Play Console account after 13 November 2023, you cannot publish to production until you have run a closed test with at least 12 testers opted in for 14 days in a row. This page explains what that means in practice, where runs go wrong, and what to do about it.
What the rule actually says
Google requires four things before it will let you apply for production access. They are simple to state and hard to satisfy:
- At least 12 testers opted in to your closed test.
- 14 consecutive days with those testers opted in. Not fourteen days total: fourteen in a row.
- Your app set up before the test starts, since the clock runs on the closed track.
- An application for production access afterwards, answering questions about the test and the app. Google says it usually reviews these within about seven days.
Until you pass, the production track and pre-registration stay locked. The rule applies to personal accounts opened after 13 November 2023; organisation accounts are not subject to it. The source is Google's own page, Testing requirements for personal developer accounts.
Where runs actually fail
Almost nobody fails because they cannot find twelve people. They fail because of what happens on day six.
Someone opts out, or uninstalls
The count drops below twelve and the consecutive-day clock restarts. A friend who clears their phone in week two costs you the whole fortnight, and you usually find out late.
You cannot see who is still in
The Play Console tells you very little day to day, so a run can look healthy until the moment you apply. Chasing people individually over chat is how most developers spend the fortnight.
Testers install and never open it again
Staying opted in is the requirement, but a test where nobody uses the app teaches you nothing about how it behaves on hardware you do not own, which is the part that bites after launch.
Running it yourself
This is a perfectly reasonable route, and worth understanding before you pay anyone. In outline:
- 01Finish your Play Console setup and upload a release to a closed track.
- 02Create a tester list of Google accounts, or a Google Group, and add at least twelve people. Email addresses must match the Google account each person uses on their phone.
- 03Send everyone the opt-in link and confirm each person actually accepted it. Accepting is a separate step from installing, and it is the one people skip.
- 04Keep all twelve opted in for fourteen consecutive days, then apply for production access.
What TesterGig does instead
We supply verified testers on real devices, keep the cohort intact for the full fourteen days, and show you a grid of who was verified on each day, so you know where the run stands without asking anybody. Testers are identified to you as T-01, T-02 and so on: you see participation, never identities. At the end you get a completion summary for the run.
We do not, and will not, ask testers for ratings or reviews. Incentivised reviews breach Google Play policy, and a run that gets your app removed is worth nothing.
Questions developers ask
How many testers does Google Play require?
At least 12 testers must be opted in to your closed test, and they must stay opted in for 14 consecutive days before you can apply for production access.
Does the 14 days have to be continuous?
Yes. The days must be consecutive. If a tester opts out and rejoins, the clock starts again, which is why a run that loses people halfway is worse than one that starts a few days later.
Who does this rule apply to?
Personal Google Play Console accounts created after 13 November 2023. Organisation accounts are not subject to it.
What happens after the 14 days?
You apply for production access from the Play Console dashboard and answer questions about the test, your app and your readiness to launch. Google says it usually reviews applications within about seven days.
Can I use friends and family as testers?
You can, and many developers start there. The difficulty is not finding twelve people once: it is twelve people who keep the app installed and open it every day for two weeks, because a single quiet stretch resets the clock.
Do testers have to use the app, or just install it?
Google requires them to be opted in for the period. Real engagement is what the requirement exists to produce, and it is also what tells you whether your app works on hardware you do not own. We verify daily usage on the device and show it to you day by day.