Closed testing basics

Google Play 12 testers, 14 days: the full guide

November 18, 2026 · 7 min read

A diverse group of young adults using mobile devices. Perfect for business and technology themes.
Photo by fauxels on Pexels

If your Google Play developer account is a personal account created after November 13, 2023, you can't publish to production straight away. Google's rule is that you "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" (App testing requirements for new personal developer accounts).

The same page says exactly when that is checked: "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." Until you meet it, Production and Pre-registration stay disabled in Play Console, and open testing "becomes available after you gain production access."

That's the whole rule. The rest of this page answers the questions that come after it, one short section each, with a link to the detailed article when you need more. Google can change these pages without notice, so check the official help page before you plan around a date.

Who the rule applies to

Google's help article describes the requirement for personal developer accounts created after November 13, 2023. It doesn't mention organization accounts. Community Product Experts describe organization accounts, and older personal accounts, as unaffected, but that isn't Google's own wording, so treat it as likely rather than certain. Personal vs organization developer accounts explains the difference, and why Google requires closed testing covers the reasoning behind the rule.

Is it 12 or 20 testers?

It's 12. The original 2023 announcement asked for 20 testers, and Google updated the same blog post in December 2024 to require "12 instead of 20 testers for personal developer accounts" (Android Developers Blog). The 14 days didn't change. Older tutorials still say 20; 20 testers vs 12 testers sorts out which advice is out of date.

What "opted in continuously" means

A tester counts once they open your opt-in link and accept it. The 14 days have to be unbroken: "Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement. If a tester opts out and opts back in later, the 14 days must be consecutive to count." Google doesn't say officially whether installing the app is part of being opted in. What counts as an opted-in tester works through examples.

Setting up the closed track

Closed testing only opens after you complete app setup. In practice that means the App content declarations, including the Data safety form, which closed tracks need even if your app collects no data. Then you create the closed track, add testers by email list or Google Group, upload a release and click Send for review on the Publishing overview page. Google says this review can take "a few hours or up to seven days (or longer in exceptional cases)", and none of that waiting counts toward your 14 days. The full walkthrough is in how to create a closed testing track. Only a closed test counts; internal testing doesn't meet the requirement (internal vs closed vs open testing).

How testers join

Testers "need a Google Account or a Google Workspace account to join a test," and they must use the Google account you added to the list. You copy the opt-in link from the track's Testers tab, but "the opt-in link displays only when an app status is 'Published'", and after the first publish it "can take several hours to become available to testers." Each tester then reads the explanation of tester responsibilities and opts in. How testers join your closed test shows the flow from their side.

Finding 12 testers

Google's own advice is to "reach out to friends, family, colleagues, or classmates", to connect with communities where potential users exist and to post about your app on social media. It also recommends testers who "represent your app's intended future audience." How to get 12 testers compares the realistic routes, and closed testing with friends and family covers the most common one and where it tends to break down.

Some developers use a paid testing service. Google's official policy doesn't mention paid testing services, so their status isn't defined by Google either way. Is paying for closed testers allowed? lays out what is and isn't documented.

During the 14 days

The count is only half of it. Google may require more testing because of "insufficient tester engagement during the testing period," so keeping the app installed and using it regularly is strongly advised. Google also recommends you "continue running closed tests while resolving user-reported issues and bugs." How to keep closed testers engaged for all 14 days has practical ideas.

What about shipping updates? Google measures the 14 days on testers' opt-in, not on a particular build, and its documentation doesn't say a new release restarts the count. That's a careful reading rather than an official statement, but it fits Google's advice to fix bugs during the test. What can hurt you is anything that takes testers out of the track, such as removing their list or their country. Details are in does updating your app reset the 14 days?

The day-by-day timeline shows how setup, testing and both reviews fit together.

Checking your count before you apply

There's no single start button: each tester's streak starts when they opt in, so in practice your 14 days start when your 12th tester joins. Having "fewer than 12 opted-in testers" is one of the reasons Google lists for asking for more testing, so check before you apply rather than after. Recruiting a few more than 12 gives you a buffer if someone drops out. How to check how many testers opted in shows where to look.

Applying for production access

Open the Dashboard in Play Console and click Apply for production. The form has three parts: your closed test (recruiting, engagement, feedback), your app (audience, value, expected installs) and your production readiness (what you changed and how you decided the app was ready). "You must summarize your testing feedback when applying for production access", and testers' feedback is under Monitor and improve > Ratings and reviews > Testing feedback. Leaving the page without clicking Next or Apply loses your answers. Step-by-step help is in how to apply for production access and our production access guide.

What Google reviews

Beyond the form, Google tells you to check app content and features (including monetization), target age group, content rating, store listing accuracy, stability, and working login credentials for reviewers. Its warning is blunt: "review is not a troubleshooting step." What Google looks at when you apply breaks each area down. On timing, Google says "review usually takes seven days or less, but can occasionally take longer," and the account owner gets an email when it's done.

If Google asks for more testing

Google's wording: "If your app requires additional testing, you may need to continue running your closed test. Reasons for required continued testing include having fewer than 12 opted-in testers or insufficient tester engagement during the testing period." Google doesn't publish a fixed waiting period before you can reapply, so keep the test running, fix the cause and reapply when you're ready. Production access rejected? What to do next goes through it.

After approval

Once you're approved, the Production page and Open testing unlock. From there you prepare your first production release, your store listing and a rollout plan. Production access approved: your next steps picks up from this point. If you're still at the start, what Google Play closed testing is is the short primer.

Quick checklist

  • Personal account created after November 13, 2023? The rule applies to you.
  • App setup and App content finished, closed track sent for review.
  • Opt-in link shared only after the track shows "Published".
  • At least 12 testers opted in, plus a few spare.
  • Testers keep the app installed and use it; you collect feedback from day one.
  • Fixes shipped on the same track; no testers or countries removed.
  • 12 or more testers with 14 unbroken days when you click Apply for production.
  • Feedback summary and "what we changed" ready before you open the form.

FAQ

Does the 12-tester rule apply to organization accounts?

Google's help page describes the rule for personal developer accounts created after November 13, 2023, and doesn't mention organization accounts. Community Product Experts say organizations aren't affected, but that isn't official Google wording.

Does internal testing count toward the 14 days?

No. Only a closed test meets the requirement. Internal testing is useful for quick checks, but it doesn't count.

Will my testers leave reviews on Google Play?

No. Google says "testers cannot leave public reviews on Google Play for test versions," and their private feedback "won't affect your app's public rating."

What happens if a tester leaves before day 14?

They don't count. You need at least 12 testers who have been opted in continuously for the 14 days before you apply, so replace anyone who leaves and count from the date the replacement joins.

Does meeting the requirement guarantee production access?

No. Meeting the 12 testers and 14 days makes you eligible to apply. Google reviews the application and makes the final decision.

If finding 12 people who stay for two weeks is the hard part, GoPlayTester provides 12+ real testers on real Android devices for the full 14 days. It helps you meet the testing requirement; Google makes the final decision. Our setup guide shows how to add the tester group, and you can see how ordering works.

All articles