Google Play closed testing
Publishing a new Android app? We run the closed test.
Google won't let a new personal developer account publish until it has run a closed test. We supply the testers, keep them opted in for the full 14 days, and send you what they found, which is exactly what Google's application asks about.
12 testers, opted in
Personal developer accounts created after 13 November 2023 need a closed test with at least 12 testers.
14 days in a row
Testers must stay opted in continuously for the 14 days before you apply. Someone who leaves starts over.
Then Google reviews it
You answer questions about the test and what you changed. Google says review usually takes 7 days or less.
When can you apply for production?
A free calculator. Nothing is sent anywhere; it runs in your browser.
The closed test most likely applies
Personal accounts created after 13 November 2023 need a closed test with at least 12 testers opted in for 14 days in a row before applying for production.
You have no margin
You meet the minimum, but one opt-out would pause your progress. Two or three spare testers protect the 14 days.
Source: Google Play Console Help. Google decides on production access; no one can guarantee approval.
Step by step
The five steps to production access
- 1
Set up a closed testing track
In Play Console, finish your app setup, then create a closed testing release and upload your build. Internal testing does not count toward the requirement.
- 2
Get at least 12 testers opted in
Add testers by email list or Google Group, share the opt-in link, and make sure each one actually accepts. Being on the list is not the same as being opted in.
- 3
Keep them opted in for 14 days in a row
Google looks at the 14 days before you apply. A tester who opts out and back in starts over, so a few spare testers protect your timeline.
- 4
Collect real feedback while they test
The application form asks what testers found and what you changed. An app that was installed and never opened is a weak answer.
- 5
Apply for production access
From the Play Console Dashboard, choose Apply for production and answer the questions. Google says review usually takes 7 days or less.
The application
What the production access form asks
Google's application has three parts. Testers who only install your app leave you with little to say in the first and third.
About your closed test
How easy it was to recruit testers, whether they used all your features, how their usage compared with what you expect in production, and a summary of their feedback and how you collected it.
Tip: Specific findings beat general praise. Mention the bugs you fixed and the devices they showed up on.
About your app
Your intended audience, what your app offers, and how many installs you expect in the first year.
Tip: Google says these answers are not shown publicly and do not affect your eligibility for developer programs.
About your production readiness
What you changed because of the closed test, and how you decided the app was ready.
Tip: This is where a written bug report helps most: you can list what was found and what was fixed.
Your options
Three ways to find your 12 testers
Friends and communities
Free in money, costly in time. Expect to recruit well over 12, since people forget to opt in or leave before day 14, and feedback tends to be light.
Tester-only services
The cheapest paid route, usually a one-time fee of roughly $15 to $50. Good if all you need is the headcount. Check how much written feedback is included.
Bugfed
The Play pass is $29 one-time: 12 testers on your closed track for 14 days, with their feedback and any bugs they find. Plans add structured bug reports and iOS and web testing for the rest of your product.
Get a Play pass, $29Not ready to pay? A free Spot Check shows you what our testers report on one flow of your app. It does not count as a closed test.
Does every Google Play developer need a closed test?
No. Google's requirement applies to personal developer accounts created after 13 November 2023. Older personal accounts are not covered, and Google's help page describes the rule for personal accounts rather than organization accounts.
Do the 12 testers have to be opted in at the same time?
Yes, in effect. When you apply, Google checks that at least 12 testers have been opted in continuously for the preceding 14 days. Testers who left before the 14 days were up do not count.
Does internal testing count?
No. Only a closed testing track counts toward the requirement.
What happens if Google says my test wasn't enough?
Google may ask you to keep running the closed test, for example if fewer than 12 testers were opted in or testers did not engage with the app. You can keep testing and apply again.
Can I upload new builds during the 14 days?
Yes. Updating the release on your closed track does not opt testers out, so fixing bugs as they are reported is normal and gives you better answers for the application form.
How does Bugfed handle the closed test?
Every Bugfed plan includes at least 12 testers who join your closed track, stay opted in for the 14 days and use the app. Their email addresses appear on your run so you can add them to your tester list. On Starter and higher plans they also file structured bug reports you can use in your application.
See what real users find in your app.
Start with a free Spot Check on one flow. If the report is useful, run your whole app next time.