ClosedTestIf you are new to Google Play, closed testing is the step you must complete before you can publish an app, if your developer account is a new personal account. This guide explains the whole process in order, in plain words, and links to a detailed guide for every step. It follows Google's own help page.
What closed testing is
Google describes closed testing as sharing your app with a targeted group of users that you control, so you can fix issues and make sure your app follows Google Play policy before launch. For new personal accounts it is also required: you must run a closed test before you apply to publish.
What the words mean
People write "closed test", "closed testing" and sometimes "close testing". On this site they all mean the Google Play test track. The same words have other meanings elsewhere. In statistics, a "closed testing procedure" is a method for comparing hypotheses. In video games, a "closed test" is a limited beta. This guide is only about Google Play.
Who needs it, and the rule
Google applies the requirement to personal developer accounts created after 13 November 2023. You must run a closed test with at least 12 testers opted in continuously for at least 14 days. Details: which accounts must run a closed test and the rule explained.
The process in six steps
- Understand the tracks. Internal, closed, open and production are different. See internal, closed and open testing.
- Set up the test. Add testers by email list or Google Group. See how to set up a closed test.
- Find your testers. Friends, communities, swap groups or a service. See how to find 12 testers and what closed testing costs.
- Run the 14 days. Instructions, reminders, a feedback record, and a buffer. See the 14-day plan.
- Prepare to apply. Check policy, stability and login details. See the production access checklist.
- Apply, and answer the form. It has three parts: your test, your app, and your readiness. See the questionnaire guide.
When something goes wrong
- A tester left: what to do.
- Testers cannot join: what to check.
- Google asked for more testing: what it means and what to do next.
All the guides, in order
The rules
- Do you need 12 testers? Which Google Play accounts must run a closed test
- Google Play's 12-tester, 14-day rule explained (2026)
- Internal, closed and open testing on Google Play: which one counts?
- Google Play closed testing FAQ: 15 questions, answered from Google's own pages
Setting up your closed test
- How to set up a Google Play closed test: testers, email lists and Google Groups
- How to find 12 testers for your Google Play closed test
- Tester swap groups and r/AndroidClosedTesting: how they work and where they fall short
- Testers cannot join your Google Play closed test: what to check
- What to tell your closed test testers: a message template
- Instructions for testers when your app needs a login or has payments
- Login details for Google Play review: how to give reviewers a working account
During the 14 days
- A 14-day plan for your Google Play closed test, day by day
- Tester engagement in a Google Play closed test: what it means and how to show it
- A tester dropped out of your Google Play closed test: what to do
- Bug report template for closed test testers (copy and paste)
- Closed test feedback record: a free template for Google's form
- How many testers should you recruit to end with 12? A rule of thumb from real data
- What 1,495 tester assignments show: how many testers really check in for 14 days
- Which Android versions do closed testers use? Data from ClosedTest's tester network
Before and after you apply
- Production access checklist: what to check before you apply
- Google Play pre-launch report: what it checks and how to use it before you apply
- Google Play production access questionnaire: what each question asks and how to answer it
- Production access form: example answers for five types of app
- Production access form: target audience, value proposition and install estimate
- Google asked for more testing: what to do next
- "Run your closed test with at least 12 testers": what Google's message means
Choosing help
- How much does Google Play closed testing really cost?
- Google Play closed testing services compared (checked 26 October 2026)
- ClosedTest vs TesterBee: an honest comparison (checked 26 October 2026)
- ClosedTest vs Testers Community: an honest comparison (checked 26 October 2026)
- Closed Test Pro vs ClosedTest: are they the same? (checked 26 October 2026)
- Is ClosedTest legit? How to check any Google Play closed testing service
Free tools
Check your numbers with the 12 tester calculator and score your preparation with the production readiness checker.
Where ClosedTest fits
If you do not want to run the 14 days yourself, ClosedTest coordinates real testers and gives you daily records and a final report. Read about us, see the pricing, the sample report, the refund policy, and how to check any service. Google makes the decision on every application, and we do not promise it.
ClosedTest is an independent service and is not affiliated with Google.