The Google Play 12 testers rule: a closed testing guide

The rule and who it applies to

The requirement targets developers with a personal Play Console account created after November 13, 2023. Before applying for production access, they must run a closed test with at least 12 testers who have been opted in continuously for at least the last 14 days.

• At least 12 testers, opted in to your closed test through the opt-in link.
• 14 days of continuous opt-in: a tester who opts out before day 14 doesn't count.
• If they opt back in, their 14 days must be consecutive — earlier days don't carry over.

Reaching 12 testers for 14 days makes you eligible to apply, not automatically approved. Google may ask for more testing, looking at things like tester engagement and whether you acted on their feedback through updates.

Setting up the closed test and inviting testers

Everything happens in Play Console, on your app's closed testing track. Menu labels move around from time to time, but the flow stays the same.

1. 1

   Prepare a test release

   Upload a build to the closed testing track and send the release for review. Testers can only install it once the release is published (status "Published").

2. 2

   Pick how you add testers

   Open Test and release > Testing > Closed testing > Manage track > Testers tab. Either email lists you manage in the console, or Google Groups. A group is handy when someone else gathers the testers for you: you just add its address in the Google Groups section.

3. 3

   Share the opt-in link

   Still in the Testers tab, copy the "Join on the web" link: that's your opt-in link, in the form https://play.google.com/apps/testing/…. Each tester opens it with the Google account you added and accepts the invitation. Being on the list isn't enough — only opted-in testers count.

4. 4

   Check installs

   Once opted in, testers install your app from Google Play like any other app and use it normally.

Checklist before launching the test

Before sharing the opt-in link, check these points in Play Console — they're the oversights that most often delay a closed test.

• The closed testing track release is published (status "Published").
• France (or each of your testers' countries) is selected under "Countries/regions" for the closed testing track.
• A feedback URL or email address is set for the closed test.
• If the app requires a login, test credentials (a demo account) are provided to testers.
• The app is free: paid apps are not supported by our service.
• Closed test testers' accounts are not added to the internal test.
• The closed testing track is not paused or deleted during the 14 days.
• Testers stay opted in until the production access application has been submitted.

The 14-day timeline

What matters is how long your testers stay opted in without a break. Try to get all 12 to opt in around the same time — otherwise your 14-day window effectively starts with the last one to join.

Before day 1

Test release available, email list or group configured, opt-in link ready to send. The more of this you prepare upfront, the faster the test can start.

Days 1 to 14

Testers stay opted in and use the app. Collect their feedback, fix what needs fixing and ship updates to the closed track — that's exactly the kind of activity Google may look at.

After day 14

If at least 12 testers stayed opted in without interruption over the last 14 days, you can apply for production access from Play Console.

Common mistakes that make the test fail

• Testers opting out midway: they drop out of the count, and opting back in doesn't recover the lost days.
• Testers added to the list who never used the opt-in link: as far as Google is concerned, they aren't taking part.
• Inactive testers: engagement is part of what Google may consider, so installing the app and forgetting it doesn't help.
• No updates for 14 days: without a new release, it's hard to show you acted on feedback.
• Starting with exactly 12 people and no buffer: a single opt-out restarts your 14-day window.

Answering the production access questions

When you apply for production access, Google asks questions about your closed test, your app, and how ready it is for production. There's no template answer, but a few principles help.

• About the test: explain how you found your testers, what they tested and what feedback came back.
• About the app: say plainly what it does and who it's for.
• About readiness: point to the fixes and updates you shipped during the test, and why you consider the app ready.
• Stick to the facts: describe what actually happened, without inflating anything.

How PlayTesterHub helps

Finding 12 people willing to stay opted in for 14 days is usually the hard part. The PlayTesterHub team runs your test on 12 physical Android devices managed in-house, in France, and gives you a group email to add in Play Console. Testing starts within 48 hours of receiving your opt-in link, and you follow progress up to 12/12 from your dashboard.

Pricing is flat and shown before any payment. PlayTesterHub does not guarantee Google Play approval — Google alone makes that call.