Google Play's 12 testers for 14 days rule: who it applies to and how to pass
Personal Google Play developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who stay opted in for 14 consecutive days, then apply for production access from the Dashboard, a review Google says usually takes seven days or less.
Who has to follow the 12 testers rule?
The rule applies to personal developer accounts created after November 13, 2023. If that is you, you cannot make an app available on Google Play until a closed test has run with at least 12 opted-in testers for 14 days in a row and Google has approved your production access application.
| Your account | 12 testers / 14 days | What you do |
|---|---|---|
| Personal, created after Nov 13, 2023 | Yes | Closed test, then Apply for production |
| Personal, created before that date | No | Release to production directly |
| Organization (any date) | No | Release to production directly |
The Dashboard in Play Console shows the testing task for the app you are working on, so check there if you are unsure. Choosing the account type is covered in Google Play developer account.
What exactly does Google count?
Google's requirement has two parts, and both are strict:
- At least 12 testers opted in to a closed test. Internal testing does not count.
- Continuously for 14 days. If a tester opts out and opts back in later, Google says the 14 days must be consecutive to count. A drop below 12 on day 10 means the clock you care about restarts.
Practically, that means you need a buffer. Invite 20 to 25 people so that a few who leave do not sink the count.
How do you set up the closed test?
- In Play Console open Test and release, Testing, Closed testing. Use the default closed track or create one.
- In the Testers tab, add testers by email list (up to 2,000 addresses per list) or by Google Group. A Google Group has no size limit and testers join it themselves, which is easier for everyone.
- Select the countries where the test is available, so testers abroad are not blocked.
- Create a release on the track: upload your App Bundle, write release notes, then review and roll out the release to the closed track.
- Copy the opt-in link from the Testers tab and send it with clear instructions: open the link with the Google Account you were invited with, accept, then install from Google Play.
- Give testers a feedback channel (an email address, a form, a chat group). Testers cannot leave public reviews on test versions, but they can send private feedback.
The first upload may show a temporary name and listing for up to 48 hours. If a tester sees "item not found", they are usually signed in to Google Play with a different account than the one on the list; see internal vs closed vs open testing for the fixes.
A worked 14-day calendar
| Day | What happens |
|---|---|
| Day 0 | Closed release rolled out; opt-in link and instructions sent to 20+ people |
| Day 1 to 2 | Chase people who have not opted in; count reaches 12 or more |
| Day 3 | First feedback round: ask testers to try one specific feature |
| Day 7 | Ship a test update that fixes the first bugs (shows you acted on feedback) |
| Day 10 | Second feedback round on onboarding, payments or the main flow |
| Day 14 or later | 14 consecutive days with 12+ opted in; open Dashboard, Apply for production |
| Up to 7 days later | Google's decision by email (usually seven days or less) |
Count your day 1 from the day you actually reached 12 opted-in testers, not from the day you sent invitations.
What does the production access application ask?
You apply from the Dashboard with Apply for production. The form has three sections:
| Section | Questions |
|---|---|
| About your closed test | How easy was it to recruit testers? Did testers use all features? Did their use match how you expect production users to use the app? What feedback did you get and how did you collect it? |
| About your app or game | Who is the target audience? What makes the app valuable or different? How many installs do you expect in the first year? |
| Production readiness | What did you change based on the closed test? How did you decide the app is ready for production? |
Answer like a short test report, with specifics. A template that works:
- Recruiting: "We invited 24 people from our beta waitlist and a local running club through a Google Group; 19 opted in within two days."
- Feature coverage: "We asked testers to complete three tasks: create a plan, log a session, restore a purchase. 15 completed all three."
- Feedback: "Collected through an in-app form and a group chat; 31 reports, 9 bugs."
- Changes: "Fixed a crash on Android 12 at sign-in, shortened onboarding from 5 to 3 screens, added an offline message."
- Readiness: "No crash reports in the last 5 days of the test; all 9 bugs closed."
Use your own real numbers. Vague answers ("testers liked it") are the easiest to reject.
Can you buy testers or use tester exchanges?
You can find paid tester services and "12 testers" exchange groups online. Weigh the risks before you use them:
- Google's ratings, reviews and installs policy bans inflating installs, ratings or reviews by illegitimate means, including incentivized reviews and automated services.
- The application asks whether testers used every feature and whether their behaviour matched your real users. Strangers who open the app once a day to keep a counter alive give you nothing true to write.
- A test that teaches you nothing means your production launch is the real test, in front of public reviewers.
The safer path is slower but honest: people from your audience, given a task and a feedback channel.
Common mistakes
- Testing on the internal track and expecting it to count.
- Inviting exactly 12 people.
- Testers opting in with a different Google Account than the one on the list.
- Forgetting to roll out a release to the closed track, so testers have nothing to install.
- Pausing the test for a big rewrite, letting opt-ins lapse and losing the consecutive days.
- Applying on day 14 with no changes made: the readiness section asks what you changed.
What happens after approval?
Once production access is granted, you create a production release as described in How to publish an app on Google Play. That release goes through the normal review, which Google says can take up to 7 days or longer in exceptional cases; timing is covered in Google Play review time.
Keep the calendar above in a shared document with your testers. Uptika helps from launch day on: its Keyword radar reads your Google Play rank for each keyword every day from launch, and Daily ping sends one morning summary of what moved. Start on the free plan, no card needed.
Questions
Does the 12 testers rule apply to organization accounts?
No. Google applies it to personal developer accounts created after November 13, 2023. Organization accounts and older personal accounts publish without it.
Do testers need to keep the app installed for 14 days?
Google's wording is that at least 12 testers must be opted in to the closed test continuously for 14 days; if a tester opts out and back in, their days must be consecutive again. The production application then asks how testers actually used the app, so a tester who joined but never opened it helps the counter and nothing else.
How do I get 12 testers for free?
Ask people who would use the app: friends, colleagues, a waitlist, an existing community or customers. A Google Group is the simplest container because it has no size limit and testers join by joining the group. Invite 20 or more so a few drop-outs do not reset your count.
What is a closed test on Google Play?
A closed test is a release track that only invited testers can join, by email list or Google Group. Testers opt in through a link and install the test version from Google Play; they can send private feedback but cannot leave public reviews.
What questions does Google ask when applying for production access?
Three groups: about the closed test (recruiting, feature coverage, whether use matched real users, feedback and how you collected it), about the app (target audience, value, estimated first-year installs) and about readiness (what you changed after the test and how you decided it is ready).
How long does production access review take?
Google says the review usually takes seven days or less, but can occasionally take longer. The account owner gets an email when it is done.