Google Play's closed testing requirement is 12 testers, not 20

Google Play requires 12 testers, not 20. The live help page says so in three separate places: "Developers with personal accounts created after November 13, 2023, 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."

If you have been trying to round up twenty people, you can stop at twelve. Recruit a few spare anyway, for reasons covered below, but the threshold you are being measured against is twelve.

What the requirement actually says

The rule lives on one page, App testing requirements for new personal developer accounts. Three statements on it matter.

On the closed testing track: "At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days."

In the summary table of track requirements: "Run a closed test with at least 12 opted-in testers continuously for 14 days. Once criteria are met, apply for production access in Play Console by answering some questions about your testing, your app, and its production readiness."

And on who it applies to: "Google Play requires personal developer accounts created after November 13, 2023, to test their apps before those apps are eligible for distribution on Google Play."

That last line is the part most often dropped. This is a rule for personal accounts created after 13 November 2023. Organisation accounts are not subject to it. Neither are older personal accounts. If you searched this question because a forum post scared you, check which kind of account you have before you do anything else.

The number is 12 in Google's docs and 20 nearly everywhere else

In February 2026, ACM Transactions on Software Engineering and Methodology published a peer-reviewed study of exactly this requirement: Grishma Shrestha, Shristi Shrestha and Anas Mahmoud, "No Country for Indie Developers: A Study of Google Play's Closed Testing Requirements for New Personal Developer Accounts", volume 35, issue 3, pages 1 to 21.

Its abstract states: "These requirements mandate that at least 20 testers must remain opted-in (use the app) for at least 14 consecutive days before the app can be published on the Play Store."

So the figure is 20 in a peer-reviewed journal article published in 2026, and 12 on Google's own help page. That is not a knock on the paper. It is the clearest possible demonstration of how sticky a stale number becomes once it is in circulation: this one cleared review at a top software engineering journal.

Reading the two sources together, the likeliest explanation is simply chronology. The paper describes the requirements as introduced in November 2023, and describes them at 20. Google's current page says 12. Twenty appears to have been the original figure and twelve the current one.

Why the wrong figure spread so far

None of the reasons are sinister, which is why it keeps happening.

It was right once. A correct number, published, then never revisited. Most guidance about the requirement was written in the panic window of late 2023 and early 2024 and has not been touched since.

Secondary sources cite each other. Blog posts cite blog posts. Videos cite blog posts. Reddit threads cite the videos. Almost nothing in that chain re-reads Google's page, because the number feels like settled background knowledge rather than something to check.

The higher number suits some people. There is a small economy of paid tester services, tester-swap groups and "get published fast" offerings. A larger requirement makes the problem sound harder and the service sound more necessary. That does not make anyone a liar, but it removes any incentive to correct downwards.

Google buried it. The requirement is a help-centre article, not a banner in Play Console with a live counter next to it. If your console told you "9 of 12 testers, day 6 of 14" the rumour would have died in a week.

The habit that fixes this is small. Open the Google page and read the number. It is one page, and it takes about twenty seconds. Do that before you trust anything written about Play policy, including this.

The paper's real finding is worth reading anyway

The tester count is a detail in that study. Its substance is what the requirement does to solo developers.

The authors analysed developer discussions of the requirements on Reddit and surveyed indie developers about compliance: "we qualitatively analyze app developers' discussions of Google Play's new closed testing requirements on Reddit. Additionally, we report insights from a survey of 14 indie app developers who recently passed the requirements or are actively seeking compliance."

Their conclusion: "Our results show that Google Play's closed testing requirements for indie apps are commonly perceived as discriminatory, imposing logistical and bureaucratic barriers on small-scale creators in their quest to compete in the mobile app market."

That finding does not change if the threshold is twelve. Twelve real humans, kept enrolled for a fortnight, is a fundraising problem rather than an engineering problem, and it lands entirely on people who do not have a company address to register with. Getting the number right makes the criticism sharper, not weaker.

What actually counts

Opted in, not installed. The measure is enrolment in the closed test, not installs, not sessions, not active users. Someone who accepts the invite and never opens the app is still opted in.

Continuously, and the clock is unforgiving. Google's page is explicit that testers who "opt in, test for fewer than 14 days, and then opt out do not count toward the requirement". If a tester leaves and rejoins, "the 14 days must be consecutive to count toward the minimum requirement". A rejoin restarts that person at day zero.

On the day you apply. You need at least 12 opted in at the moment you apply, and each of them opted in for the preceding 14 days. It is not a peak figure you hit once.

The traps follow from those three facts:

• A tester who installs, looks around and deletes the app has usually left the app installed but may also have left the programme. Deleting the app is not always opting out, but opting out is what breaks the run.
• Watching install counts instead of opt-in counts. They diverge.
• Assuming a testers list of twelve is twelve opted-in testers. People accept invitations and then leave; the list does not.

How to run it so it works first time

1. Recruit 15 to 18, not 12. Attrition over a fortnight is normal and each departure costs you 14 days for that slot.
2. Tell them plainly not to leave the test. Google says this too: "Important: Inform your testers that they need to remain opted in to your closed test continuously for at least 14 days." One message on day one, one reminder around day seven.
3. Do not stop the test when you apply. Keep it running through review.
4. Collect feedback as you go, because you will be asked to summarise it. In Play Console it is under Monitor and improve > Ratings and reviews > Testing feedback.
5. Apply once the 14 days are complete, and answer the three sections honestly: 'About your closed test', 'About your app/game', 'About your production readiness'.
6. Expect to wait. Google's page says: "Review usually takes seven days or less."

One sequencing detail that catches people: open testing is not a shortcut. It only becomes available after you gain production access, so you cannot use a public beta to recruit the testers who unlock production.

The mechanics of setting the test up, inviting people and tracking the window are covered in the companion how-to, google-closed-testing-requirements. AppSubmit tracks the opt-in count and the 14-day window against the requirement as Google currently states it, which is the same thing you can do with the Play Console testers list and a calendar reminder.

Source

Google Play Console Help, App testing requirements for new personal developer accounts: https://support.google.com/googleplay/android-developer/answer/14151465

Shrestha, G., Shrestha, S. and Mahmoud, A. (2026) "No Country for Indie Developers: A Study of Google Play's Closed Testing Requirements for New Personal Developer Accounts", ACM Transactions on Software Engineering and Methodology, 35(3), 1 to 21. https://doi.org/10.1145/3736578