Subscribe
App Growth Q&AFacts as of

12 Testers for 14 Days: Pass Google Play Closed Testing

The short answer

How do you pass Google Play's 12 testers for 14 days rule?

Run a closed test, not an internal one, with at least 12 testers who stay opted in for 14 days in a row, and have 12 opted in on the day you apply. The count alone isn't enough: Google can send you back to testing for insufficient tester engagement. Give testers tasks, collect their feedback and ship an update from it.

Key facts

Chapters

  1. 0:0012 testers for 14 days: the short answer
  2. 0:26Does the 12 testers rule apply to your account?
  3. 1:11Are 12 testers really opted in to your closed test?
  4. 2:01Are the 14 days unbroken?
  5. 2:39Why does Google say "more testing needed"?
  6. 3:53What does Apply for production ask?
  7. 4:50What changed the second time?

Transcript

Edited for reading

Jade is a fictional budgeting app and its numbers are illustrative. Every rule on this page comes from Google's own Play Console Help pages, listed under Sources.

12 testers for 14 days: the short answerWatch from 0:00

Twelve testers. Fourteen days. And Google can still say no.

If you're a solo developer stuck on closed testing, here's the short answer. Twelve testers have to stay opted in for fourteen days in a row. And Google's own help page says it checks whether they actually used your app.

Five checks, in the order that saves you the most time. We'll follow Jade, a made-up budgeting app that had fourteen testers and still got sent back.

Does the 12 testers rule apply to your account?Watch from 0:26

Check one. Until you pass, the Production button stays locked. Pre-registration stays locked too.

The rule covers personal Play Console accounts created after November 13, 2023. New personal accounts also have to verify a real Android phone, using the Play Console app. Google says the rule protects users from low-quality apps, malware and fraud.

And if an older guide says twenty testers, that changed. Since December 2024, it's twelve.

The rule is written for personal accounts. Organisation accounts aren't named in it. But an organisation account is meant for a real business. It needs a business ID called a D-U-N-S number.

Our take: don't switch just to skip the test.

Are 12 testers really opted in to your closed test?Watch from 1:11

Check two. Are twelve people really opted in?

It has to be a closed test. The rule names closed testing, not internal. And someone in your internal test has to leave it before they can join the closed one.

Add testers by email list or by Google Group. Every tester needs a Google account. In Play Console, that's Test and release, then Testing, then Closed testing, then Manage track.

Then each person has to tap the opt-in link themselves. Being on your list isn't the same as being opted in. The link only shows up once the closed track is published. It can take several hours to work.

Check your countries too. They apply to every track, so a friend abroad may not get the build. And if your app is paid, closed testers have to buy it.

Our take: invite fifteen or more, not twelve. Someone always drops out.

Are the 14 days unbroken?Watch from 2:01

Check three. Are the fourteen days unbroken?

Google counts days per tester, and they have to be in a row. A tester who opts out before day fourteen doesn't count. If they come back, their fourteen days have to be in a row again.

And you need twelve of them opted in on the day you apply, plus the fourteen days before it. Google never says the whole test restarts. It counts each tester's own unbroken run.

Jade invited fourteen friends. Two opted out on day nine. So only twelve had a full run. Just enough.

Google even tells you to warn testers to stay in. So tell them on day one.

Why does Google say "more testing needed"?Watch from 2:39

Check four. Did they actually test it? This is where Jade failed.

Google says the reasons it sends an app back to testing include two. One is fewer than twelve opted-in testers. Jade had twelve. So what's the other one? Not enough tester engagement.

Most of Jade's friends opened it once, looked at one budget screen, and never came back.

Google doesn't publish a number for engagement. But its form asks whether testers used all the features, and whether they behaved like real users.

So give your testers jobs. Day one, add an account. Day three, set a budget. Day seven, send feedback. Put the jobs in a group chat, and check in on day ten. That's when people drift.

Then ship an update to the closed track that fixes what they found. That's your proof you listened.

What about tester-swap groups and paid tester services? Google doesn't name them. But its form asks if usage matched real users, and its policy bans inflating installs by illegitimate means. Those are Google's words. Calling swaps risky is our read, not a Google rule.

What does Apply for production ask?Watch from 3:53

Check five. What does the application ask? When the twelve and the fourteen are done, open the Dashboard and click Apply for production.

The form has three parts: your closed test, your app, and your production readiness.

Part one asks how easy recruiting was, whether testers used every feature, and what feedback you got. You have to summarize that feedback, so keep a record from day one. Their feedback lands in Play Console, under Testing feedback.

Part two asks for your audience, your app's value, and your expected installs in year one. Google says those answers aren't shown publicly.

Part three asks what you changed because of the test, and how you knew you were ready.

Our take: that's where most answers go thin. Nothing changed tells Google the test didn't matter.

Review usually takes seven days or less. Sometimes longer. And review isn't a bug hunt. A crash or a broken test login can still get you refused.

What changed the second time?Watch from 4:50

So what changed for Jade the second time? It kept the closed test running, as Google says you may need to. It added six more friends, gave everyone three tasks, and shipped two updates from their feedback. Then it answered part three with those two updates.

In our made-up example, production access came through.

The count gets you to the button. The testing gets you through it.

Sources

  1. Play Console Help, App testing requirements for new personal developer accounts (25 October 2026)
  2. Play Console Help, Set up an open, closed, or internal test (25 October 2026)
  3. Play Console Help, Get started with Play Console (25 October 2026)
  4. Play Console Help, Choose a developer account type (25 October 2026)
  5. Play Console Help, Device verification requirements for new developer accounts (25 October 2026)
  6. Google Play policy, User Ratings, Reviews, and Installs (25 October 2026)
  7. Android Developers Blog, Ensuring high-quality apps on Google Play (updated 11 Dec 2024: 12 instead of 20 testers) (9 November 2023)

Caveat: Google publishes no engagement threshold, no full list of refusal reasons and no waiting period before you reapply. The rule names personal accounts; Google doesn't use the word "exempt" for organisation accounts. Google doesn't name tester-swap groups or paid tester services; calling them risky is our read of its policy wording, not a Google rule. Screens in the video are simplified diagrams, not Google's interface.

Watch next