Google Play's 12 testers for 14 days rule, explained

What the rule actually says

Google's own wording is precise: developers with a newer personal account must "run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days". Until that bar is met, the Production and Pre-registration tracks stay disabled in the Play Console — you can still upload builds, you just cannot release them to the public.

The requirement is per app, not per account. Every new app on an affected account goes through its own closed test before it can reach production. The upside is that once an app has production access, updates to that app are published the normal way.

Who the rule applies to

Google introduced the closed-testing requirement for personal developer accounts created after 13 November 2023. If you registered as an individual on or after that date, expect to see the requirement on every new app's dashboard.

Organisation accounts — the ones registered with a D-U-N-S number on behalf of a company — are not subject to the testing requirement under the current policy, and neither are personal accounts created before the cut-off. That said, Google adjusts policy over time, so treat the dashboard, not this guide, as the final word for your account.

• Personal account created after 13 November 2023 → the rule applies to each new app.
• Personal account created before that date → not subject to the rule today.
• Organisation account → not subject to the rule today.

What counts as an opted-in tester

A tester counts when they are opted in to your app's closed testing track. In practice that means they opened your opt-in link (or were on the email list or Google Group you attached to the track), accepted the invitation, and installed the app from Google Play while signed in to the same Google account.

Whether the tester is a friend, a colleague or a stranger makes no difference to the count. It does make a difference to the review that comes later: Google looks at whether testers actually used the app, so twelve people who installed it once and never opened it again are a weak foundation for your production application.

• Opted in through the closed track — not just someone who sideloaded an APK.
• Installed from Google Play with the same account that opted in.
• Stayed opted in for the whole window rather than leaving and rejoining.
• Used the app during the period, so there is real engagement to point to.

What resets the 14-day clock — and what does not

The 14 days are counted per tester and must be consecutive. A tester who opts in, tests for a week and opts out does not count. If the same person opts in again later, their 14 days start from the new opt-in date. That is why a single early drop-out can quietly push your timeline back, even if a replacement joins the next day.

Publishing a new build to the same closed track does not remove anyone's opt-in, so shipping fixes during the test is fine — and usually a good idea, because it gives testers a reason to open the app again and gives you something concrete to describe in your production application.

How the testing tracks fit together

The Play Console has four release tracks, and only one of them counts towards the requirement.

1. 1Internal testing — optional, up to a small list of trusted testers, no requirements. Useful for smoke-testing a build before the real test starts, but days spent here do not count.
2. 2Closed testing — the track Google measures. Complete your app setup, create the track, attach a tester list, and start the 14-day window once 12 testers are opted in.
3. 3Production access application — once the closed test meets the bar, apply from the dashboard. Google reviews the answers and the test itself.
4. 4Open testing and Production — both unlock only after production access is granted.

A realistic timeline

Developers often read "14 days" and plan for two weeks. The real timeline is longer, because the window only starts once 12 testers are opted in, and the review happens after it ends.

• 1–3 days: finish the store listing, content rating and data safety form, upload the build and create the closed track.
• A few days to a few weeks: recruit 12 testers (this is the step most developers underestimate — see the guide on finding testers).
• 14 days: the continuous testing window.
• Up to about 7 days: Google's review of your production access application, sometimes longer.

How TesterMandi fits in

TesterMandi exists because recruiting 12 strangers who stay for 14 days is the hardest part of the process. Post your app in the TesterMandi Android app and choose a plan: with Play Console Approval, 12 genuine testers join your closed test with daily proof of participation; Genuine Feedback & Testing adds genuine feedback and a detailed testing report at the end.

TesterMandi helps developers organize and participate in testing. Google Play production approval is determined solely by Google and cannot be guaranteed by TesterMandi.