What is the 12 testers requirement?
Before you can publish an Android app to the production track on Google Play, Google requires that your app goes through a closed testing phase. Specifically, you need at least 12 testers who opt in to your closed test, and those testers must remain active for a minimum of 14 consecutive days.
This policy was introduced by Google to improve the overall quality of apps on the Play Store. The idea is simple: if your app has been tested by real users for at least two weeks, it is more likely to be stable, functional, and ready for a wider audience. If you just want to get started right away, check out our step-by-step guide to using Get12Testers.
Why did Google introduce this rule?
Google Play has dealt with a massive volume of low-quality apps, spam, and even malicious software for years. The 12 testers requirement is part of a broader push to raise the bar for new apps entering the store.
Here is what Google is trying to accomplish:
- Reduce spam and throwaway apps. Requiring a 14-day closed test makes it harder for bad actors to flood the store with auto-generated or low-effort apps.
- Catch bugs early. Real users testing your app before launch helps surface crashes, usability issues, and broken features that automated testing might miss.
- Encourage developer accountability. If you have 12 people willing to test your app, it signals that you are serious about your project.
- Protect end users. Apps that have gone through closed testing are less likely to crash or behave unexpectedly when they reach the general public.
What exactly are the requirements?
Let's break it down step by step:
- Create a closed testing track. In the Google Play Console, go to Testing > Closed testing and create a new track (or use the default one).
- Upload your app bundle. You need a signed AAB (Android App Bundle) uploaded to the closed testing track. APKs are no longer accepted for new submissions.
- Add at least 12 testers. You can add testers by email address or by creating a Google Group. Each tester needs a Google account.
- Testers must opt in. It is not enough to just add email addresses. Each tester must click the opt-in link and actually join the test. Google tracks this.
- Wait 14 days. The 14-day clock starts once you have at least 12 opted-in testers. The testers need to remain opted in for the full 14 days. If testers drop out and you fall below 12, the clock may reset.
- Testers should actually use the app. While Google does not publicly specify exact usage metrics, there is strong evidence that testers who opt in but never install or open the app may not count toward the requirement. Google wants real engagement, not just names on a list.
Common mistakes developers make
Mistake 1: Adding testers who never opt in
You might add 20 email addresses to your closed test, but if only 8 of them click the opt-in link, you only have 8 testers. You need 12 actual opt-ins.
Mistake 2: Using fake or throwaway accounts
Some developers create 12 Google accounts themselves and try to fake the testing process. Google has become very good at detecting this. Accounts that share the same device, IP address, or behavioral patterns will likely not count. Worse, it could flag your developer account for policy violations.
Mistake 3: Not waiting the full 14 days
The 14-day period is strict. Day 13 is not day 14. If you try to apply for production access before the full 14 days have passed, your request will be denied. Be patient and wait it out. If your production access does get rejected, read our guide on how to fix a rejected production access request.
Mistake 4: Ignoring tester feedback
While Google does not technically require you to act on feedback during the closed test, the entire point is to improve your app. If testers report bugs and you ignore them, you are missing a valuable opportunity to launch with a better product.
Mistake 5: Thinking the requirement is optional
This is not optional. If you are a new developer account or if your app is brand new, you cannot skip this step. Google will block your production release until the closed testing requirement is met.
Who does this requirement apply to?
The 12 testers requirement applies to:
- New developer accounts publishing their first app.
- New apps being published for the first time, even on established developer accounts.
- Apps that have been removed and are being re-published.
If you already have apps on the Play Store and you are publishing an update (not a new app), this requirement does not apply to that update. But any net-new app listing will need to go through closed testing.
How long does the whole process take?
At minimum, expect about 2 to 3 weeks from start to finish:
- Days 1 to 3: Set up your closed testing track, upload your app bundle, and start recruiting testers.
- Days 3 to 7: Get all 12 testers to opt in. This is often the hardest part because it requires coordination and follow-up.
- Days 7 to 21: Wait for the 14-day testing period to complete.
- Day 21+: Apply for production access. Google may take an additional few days to review your app.
In practice, many developers report the process taking 3 to 4 weeks total because finding 12 willing testers is harder than it sounds.
Where do you find 12 testers?
This is the question every indie developer asks. Here are the most common approaches, along with their pros and cons:
Friends and family
The obvious first choice. The problem is that most people will say "sure, I'll test it" and then never click the opt-in link. You also need 12 people with Android devices and Google accounts who will stay opted in for two weeks.
Online communities
Reddit (r/AndroidDev, r/testing), Discord servers, and developer forums are common places to recruit testers. The downside is that you are competing with many other developers making the same request, and there is no guarantee anyone will follow through.
Tester exchange services
Some platforms let developers trade testing. You test someone else's app, and they test yours. The quality of feedback varies widely, and some of these services are borderline against Google's policies if they involve fake engagement.
Get12Testers
This is exactly why we built Get12Testers. Instead of begging strangers on Reddit or coordinating with unreliable volunteers, you join a community of Android developers who all need the same thing. You test other developers' apps to earn credits, then spend those credits to get your own app tested. Everyone benefits, the feedback is structured and real, and you meet Google's requirements without spending a dime. Read our complete walkthrough of how the platform works.
Tips for a smooth closed testing experience
Prepare your app bundle properly. Make sure your AAB is signed correctly and your app is in a testable state. Testers will lose interest quickly if the app crashes on launch.
Write clear tester instructions. When you share the opt-in link, include a brief message explaining what the app does, what you want testers to focus on, and how long the test will last. People are more likely to participate if they know what is expected.
Follow up with your testers. A gentle reminder after a few days goes a long way. Not everyone will opt in immediately, and some people need a nudge.
Use the testing period wisely. Do not just sit and wait for 14 days. Monitor crash reports in the Play Console, watch for feedback, and push updates to your closed test if needed. You can update your app during the testing period without resetting the 14-day clock.
Test on multiple devices. Ask your testers what devices they are using. The more device diversity you have, the more confident you can be that your app works broadly.
What happens after the 14 days?
Once your 14-day closed testing period is complete, you can request production access in the Google Play Console. Google will ask you to fill out a detailed form about your testing process — we cover exactly how to answer those questions and avoid rejection. Here is what to expect:
- Go to your app's dashboard in the Play Console.
- Navigate to Production and click "Create new release."
- Google will review your app. This review can take anywhere from a few hours to several days.
- If approved, your app goes live on the Play Store.
Keep in mind that passing the closed testing requirement does not guarantee your app will pass Google's content review. Your app still needs to comply with all Google Play policies, including content guidelines, privacy requirements, and technical standards.
Frequently asked questions
Can I use the same testers for multiple apps?
Yes. The same people can opt in to test multiple apps. There is no restriction on this.
Do testers need to leave a review?
No. Closed testing does not involve public reviews. Testers just need to opt in, install the app, and use it.
What if a tester uninstalls the app?
Uninstalling is not the same as opting out. As long as the tester remains opted in to the test, they count toward your 12 even if they uninstall the app. However, Google may look at engagement signals, so having testers who actually use the app is better.
Can I run a closed test and an open test at the same time?
Yes. You can have both a closed and an open testing track active simultaneously. However, only the closed test counts toward the 12 testers requirement.
Does the 14-day period reset if I push an update?
No. Pushing an update to your closed testing track does not reset the 14-day clock. The clock is based on when you had 12 opted-in testers, not on when you last uploaded a build.
What if I already have an app on the Play Store?
If you already have a published app and you are adding a new, separate app, the new app will still need to go through the closed testing process. Existing apps that are already live are not affected.
The bottom line
Google's 12 testers requirement is not going away. It is a permanent part of the app publishing process on Google Play. The sooner you accept it and plan for it, the smoother your launch will be.
The biggest challenge is not the 14-day wait. It is finding 12 real people who will actually opt in and stick around. That is the problem Get12Testers solves. Instead of scrambling to find testers at the last minute, you build up credits by testing other apps, and when you are ready to launch, your testers are already waiting. Here is exactly how the platform works, step by step.
Stop treating closed testing as an obstacle. Treat it as your first round of real user feedback. Your app will be better for it.
Related reading: