Google Play Closed Testing: 12 Testers for 14 Days

If you have a new personal developer account, the Google Play closed testing rule of 12 testers for 14 days is the first real hurdle before launch. Google requires personal accounts created after November 13, 2023 to run a closed test with a minimum of 12 testers who have been opted in continuously for at least 14 days. Only after that can you apply for production access.

This guide explains what each part of the rule means, based on Google's own Help Center article, App testing requirements for new personal developer accounts, and the common mistakes Google's documentation warns about.

The rule in one sentence

Google's wording is direct: 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. When you meet those criteria, you can apply for production access from the Dashboard in Play Console.

Until then, some parts of Play Console stay switched off. Google names two of them: the Production page and Pre-registration. Both remain disabled until the testing requirements are met. That is why the rule matters so much in practice. It is not a recommendation you can skip; it decides when your app can reach users on Google Play at all.

The rule has three parts, and each one is easy to get slightly wrong:

• A closed test. Not an internal test and not an open test.
• At least 12 testers opted in. Testers who were invited but never opted in do not count.
• Continuously for at least 14 days. The count is about the 14 days before you apply, without breaks.

Who does the rule apply to?

Google's article is written for personal developer accounts created after November 13, 2023. If your account matches both, the requirement applies to you before your first app can go to production.

Google offers two account types, personal and organization, and describes them as having access to the same functionality. The testing requirement is described for personal accounts. If you are not sure which type you have, or whether the rule covers it, read our guide to Google Play closed testing requirements, which compares the two account types using Google's own definitions.

What counts as one of your 12 testers?

The number Google checks is the number of testers who are opted in to your closed test when you apply. Google states that at least 12 testers must be opted in to your closed test at that moment, and that they must have been opted in continuously for the preceding 14 days.

Opting in is an action the tester takes. Google's setup article explains that a user is eligible for a test track only when two conditions are both true: the user is included in the track's tester configuration, and the user actively opts in to the test. Adding someone's email address to your tester list is only the first half. Until they open your opt-in link and accept, they are not counted.

A few other details from Google's documentation shape who can be a tester:

• To join a test, a user needs a Google Account or a Google Workspace account.
• A user who opts in to your internal test is not eligible for your closed or open test. To join the closed test, that user must first opt out of the internal test and then opt in to the closed test.
• If your app is paid, Google notes that testers must purchase it when taking part in an open or closed test.

Twelve is the minimum, not a target. If you have exactly 12 opted-in testers and one drops out on day 13, you are below the line. Recruiting more than 12 gives you a margin.

What does “14 continuous days” mean?

The most misunderstood part of the rule is the word continuously. Google answers it in the FAQ of its testing requirements article: 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 toward the minimum of 12 continuously opted-in testers.

In practice that means:

• A tester who joins on day one and stays opted in for the whole period counts.
• A tester who joins, leaves after a week and rejoins starts again. Only an unbroken run of 14 days counts.
• The 14 days are measured back from the day you apply. Google's wording is that testers must have been opted in continuously for the preceding 14 days.

Google's own advice is simple: inform your testers that they need to remain opted in to your closed test continuously for at least 14 days. It is worth saying this clearly when you invite people, because a tester leaving the test is an easy way for the count to drop without you noticing. Our tester invitation template includes it in both versions.

Recruiting and engaging testers

Google's testing requirements article includes its own guidance on finding testers and keeping them involved. On recruitment, Google says the most common way to recruit testers is through personal and professional networks: friends, family, colleagues or classmates. It also suggests connecting with communities where potential users already are. For example, for an app built for fitness enthusiasts, Google suggests approaching local clubs or connecting with target users in online groups. You can also post about your app on social media and invite followers to sign up.

Google recommends recruiting a diverse group, so you catch bugs and usability issues that might affect specific user groups or device types, and recruiting testers who represent your app's intended audience. Its example is a productivity app for businesses, where it suggests recruiting business professionals from various target industries. In Google's words, the closer your test users align with your target audience, the more useful feedback you receive.

On engagement, Google's advice is practical:

• Give testers clear instructions on how to test your app and report bugs, and say what type of feedback you want.
• Encourage testers to use as many features as possible, so the feedback covers the whole app.
• Provide a clear feedback channel, such as email, a website or a messaging forum. Testers can also send private feedback directly through Google Play.
• Tell testers that they need to remain opted in to your closed test continuously for at least 14 days.

Google also suggests inviting closed testers to a messaging group where feedback can be shared among participants, because testers can add context that helps you prioritize updates.

How do you keep track of opted-in testers?

Google's Help Center pages explain the requirement and where you apply, which is the Dashboard. The pages we checked do not describe a specific screen for watching the opted-in count day by day, so we will not invent one here.

What you can control is your own record. A simple sheet with each tester's name, the Google account email they joined with and the date they opted in makes it easy to see when the 14 days end, and who you need to remind to stay in. Our closed testing tracker template is a ready-made version of that sheet. Ask every tester to confirm once they have opted in. Google's setup article explains that after clicking your opt-in link, testers see an explanation of tester responsibilities and a link to opt in, and each tester needs to opt in themselves. Nobody can do it on their behalf.

Your record also helps later. When you apply for production access, Google asks you to summarize the feedback you received and to describe how testers engaged with your app. Notes kept during the test are far easier than reconstructing two weeks from memory.

Common mistakes that cost days

Several avoidable problems can cost you days. Each item below is based on something Google documents.

• Counting invites instead of opt-ins. An email on your list is not an opted-in tester until that person accepts through the opt-in link.
• Testers stuck on the internal track. Anyone opted in to your internal test is not eligible for the closed test until they opt out of internal testing and opt in to the closed test.
• Sharing the link before the app is published to the track. Google notes that the opt-in link displays only when the app status is 'Published'. Apps in 'Draft' or 'Pending publication' status do not show it. After the first publication of a test, the link can take several hours to become available.
• Google Group members who never joined the group. For closed tests that use a Google Group, users must join the group before they can opt in.
• Testers leaving early. Anyone who opts out restarts their own 14 days if they come back.
• Low engagement. Google lists insufficient tester engagement during the testing period as a reason an app may need continued testing, alongside having fewer than 12 opted-in testers.
• No way to collect feedback. Testers cannot leave public reviews on test versions, so give them a direct channel such as email or a website, in addition to private feedback through Google Play.

What happens after the 14 days?

Once you have at least 12 testers who have been opted in continuously for the preceding 14 days, you can apply. Google's steps are to open the Dashboard in Play Console and click Apply for production. The application has three sections: about your closed test, about your app or game, and about your production readiness.

Google reviews the application and emails the account owner when the review is complete. Google says the review usually takes seven days or less, but can occasionally take longer. Our guide to applying for production access on Google Play walks through each section of the form.

Frequently asked questions