If you’ve recently created a personal Google Play developer account and are ready to publish your app, you might have encountered the term “12 testers for 14 days policy”. This requirement was introduced by Google Play in November 2023 and aims to improve the quality of apps in the Google Play Store. Here’s a detailed breakdown of what the policy entails and how to navigate it efficiently.
What is Google Play’s 12 Testers for 14 Days Policy ?
To publish an app on the Play Store, developers must run a closed test with at least 12 testers continuously over 14 days. These testers must opt-in and actively engage with your app. You need to fulfill the below points.
- Have at least 12 testers install your app
- Keep these testers opted-in for 14 continuous days
- This policy will only apply to personal google play console accounts created after 13th November 2023.
Pro Tips
Join 50,000+ devs using our free Testers Community app to get 12 testers in 24 hours. 10,000+ apps got production access. Rated 4.6★ on Google Play 🙌.
How to get 12 Testers for 14 Days ?
There is no single trick to it. Below are the four most reliable ways developers get 12 active testers, from completely free to fully done for you. Pick the one that matches your budget and timeline.
1. Testers Community free app (best free option)
We built a free community of 50,000+ developers where everyone helps each other pass closed testing. You test a few other apps to earn credits, then post your own app and get 12 testers within 24 hours, at no cost. More than 10,000 apps have reached production access this way.
- Download the Testers Community app from Google Play (free, rated 4.6 stars).
- Test 3 other developers’ apps to earn 60 credits. This only takes about 15 to 20 minutes.
- Post your own app link to a Pack, a group of developers who test each other’s apps.
- Your 12 testers opt in and keep your closed test running for the full 14 days.
You can read more about how the community works here.
2. Testers Community professional service (fastest and guaranteed)
If you would rather not test other apps or wait, the paid service assigns verified, actively engaged testers within 6 hours. It is the fastest and safest way to run your closed test with genuinely engaged people, which is exactly what Google checks at production review.
- Starter ($15): 15 verified testers, more than Google’s minimum of 12.
- Pro ($25): 25 verified testers plus a detailed store listing (ASO) report and priority support.
- Testers start within 6 hours of checkout.
- Every plan is backed by a production access guarantee, or a full refund.
3. Friends, family and social media
You can ask people you know to join your closed test. It is free, but it is the least reliable option, because keeping 12 people genuinely engaged for two full weeks is hard.
- Many people agree but never click the opt-in link.
- Testers install once and never open the app again.
- Friends with iPhones cannot help, since this is Android only.
4. Reddit and developer communities
Communities on Reddit, Discord and developer forums often run tester exchange threads: you test their app, they test yours. It works, but it is slow and needs you to stay active.
- Our own subreddit r/androidapptesting is the best place to start, along with r/testerscommunity, r/AndroidDev and r/AppTesting.
- Read each community’s self promotion rules before posting.
- This is essentially what the Testers Community app automates at scale.
Engagement matters more than the number. Twelve people who install and never open your app can still get you rejected. If engagement is weak, Google rejects your app at production review and asks you to test again for another 14 days, and that cycle repeats until your testers are genuinely active. Real, engaged testers are the only way out.
Free vs paid: which should you choose?
| Free community app | Paid service | |
|---|---|---|
| Price | $0 | $15 to $25 |
| Testers | 12 | 15 (Starter) or 25 (Pro) |
| Time to get testers | About a day | Within 6 hours |
| Guarantee | None | Production access, or a full refund |
| Effort | Test 3 apps first | Just submit your app |
| Best for | Tight budgets | Speed and certainty |
Tips to get accepted, not rejected
- Aim for more than 12 active testers. A buffer of 15 to 25 protects you if a few go quiet.
- Prioritize engagement over headcount. Ask testers to open your app on several different days.
- Share the opt-in link, not the store link. Installs from the store do not count toward closed testing.
- Make sure your app does not crash on launch. Crashes kill engagement fast.
- Answer the production access questions fully. Incomplete answers are a listed rejection reason.
FAQ’s on 12 Testers Policy
You might have got multiple doubts while reading through this article. You are not alone on those questions and you can find answers to most of those questions below.
1. What if any of the testers uninstall the app before 14 days ☹️?
Google states that once a tester opts in, they count toward your 14-day requirement even if they uninstall the app. You don’t need to worry about uninstalls breaking your closed test.
2. How to opt out of the app testing program?
Testers can only opt out via the testing web link. Visiting the app’s testing page will show an “Opt out” button. Simply uninstalling the app does not opt them out.
3. How many testers are needed to get production access?
The requirement is 12 active testers for 14 consecutive days. Note that having more than 95 testers also won’t guarantee approval. Google evaluates many factors beyond tester count. Once you have 12 testers, the 14-day clock starts and you must follow Google’s guidance to request production access.
Read more here: https://www.testerscommunity.com/blog/google-play-production-access-rejected
4. How to publish an app on the Play Store without 12 testers 😤?
If you have an organisational Play Console account, or your personal account was created before November 13, 2023, you don’t need any testers. Otherwise, the 12-tester requirement applies.
5. Do we need 12 testers every time we publish a new app?
Yes, you need to find 12 testers for every new app you publish on play store. Once you got the production access for an app, you don’t need 12 testers again to release updates to that app.
6. How to get 12 testers for free?
Download the Testers Community app from Google Play (https://play.google.com/store/apps/details?id=com.testerscommunity) and post your closed-test link, and our community will help you find 12 testers at no cost.
7. Do we need to test our app for 14 days continuously?
Testers don’t have to open the app every single day. What matters is that you collect meaningful feedback over the 14-day window and improve the app accordingly.
8. Google Play “12 Testers” vs. “20 Testers” policy?
It’s the same closed-testing policy, but new personal accounts now only require 12 testers instead of 20 to qualify for production access.
9. What is Google Play’s “12 testers for 14 days” policy?
In simple terms, developers need to test their apps with 12 testers for 14 days continuously to publish their apps on play store. It is mandatory for all the apps you publish on play store. It only applies to personal Google Play Console accounts created after November 13, 2023.
10. What are the different testing tracks in Play Console?
- Internal Testing: Quick distribution to a small group (up to 100 testers) for early feedback.
- Closed Testing: Required for production access; needs 12 testers opted in for 14 days.
- Open Testing: Public beta before production; available after closed-testing requirements are met.
- Production: Full app availability on Google Play;
Conclusion
We really feel this is a very important and useful move for individual developers. But this doesn’t mean we will be getting production access very easily. During the previous policy of “12 testers for 14 days”, we have seen apps with more than 80+ testers got production access rejected. So for Google is not about “number of testers”, there are a lot of factors Google takes into account before giving access to production. You can read this blog to avoid production access rejection.
You can see more discussion about Google Play Console at r/TestersCommunity
