How to Get 12 Testers for Google Play Closed Testing
Five ways to find 12 testers, the mistakes that break the 14-day count, and how to keep testers active.
Read the guide →Google Play 14-Day Closed Testing Requirement Explained
Google Play now asks many new developers to show that their app works with real testers before it goes public. Here is who the rule covers, what you have to do, how long it takes, and how to answer the production access questionnaire.
Who has to run the closed test
The rule applies to personal Google Play Console accounts created after November 13, 2023. Until you meet the testing requirements, Production and Pre-registration stay locked for your apps.
The requirement is described for personal accounts. If you are unsure what applies to your account, check the message on your Play Console Dashboard and read Google's Play Console Help page.
The rules in short
- Run a closed test for your app.
- Have at least 12 testers opted in.
- Each tester must stay opted in for 14 consecutive days.
- When you meet the criteria, open the Dashboard and select Apply for production.
Watch out: A tester who opts in, tests for less than 14 days and then leaves does not count. If someone leaves and rejoins, the 14 days must still be unbroken. Tell every tester to stay opted in.
The timeline step by step
- Roll out to the closed trackUpload your app build and release it to your closed testing track.
- Add testers and share the linkAdd your testers and send them the opt-in link. After the first publication, the link can take several hours to start working.
- Keep 12 or more testers opted inEach tester needs 14 consecutive days. Ask them to join early and stay.
- Apply for productionOpen the Dashboard, select Apply for production and complete the questionnaire.
- Wait for the reviewGoogle says it usually finishes the review within seven days, but it can take longer.
Plan for about three weeks from the day your testers first opt in to a production decision. Allow more time if you need to fix problems or recruit more testers.
The production access questionnaire
The form has three parts. Here is what each one asks and how to answer well.
About your closed test
Google asks how easy it was to recruit testers, how they engaged with your features and whether their usage resembled real users, and what feedback you collected and how. Be specific. Name the features testers used, the feedback you received and where it came from.
About your app
You describe your target audience, the value your app offers (or what makes your game unique), and the number of installs you expect in the first year. Give a realistic estimate and explain the real problem your app solves.
Production readiness
You explain which changes you made based on testing and how you decided the app is ready for release. List real fixes, such as crash fixes, layout changes or faster loading screens.
Note: The wording of the form can change, so read the current version in Play Console before you answer.
What if Google says you are not ready
If you have too few opted-in testers or weak tester engagement, Google may ask you to keep your closed test running. You can fix this by:
- adding more testers so you stay above 12 even if someone leaves
- asking testers to complete specific tasks in your app
- fixing the problems they report and releasing an update
- running the test for more days, then applying again
Common questions
Can friends and family be my testers?
Yes, as long as they are real people with Google accounts who opt in, install the app and use it. The questionnaire asks how you recruited testers, so be honest about it.
How many testers should I add?
Google requires at least 12 opted in. Adding a few extra gives you a buffer if someone drops out.
When do the 14 days start?
The 14 days are counted for each tester from when they opt in, and they must be consecutive. Ask everyone to join early.
How we can help
12AppTesting provides 12, 15 or 20 real Android testers on physical devices who test daily for 14 days, plus 7 extra days of support and help with the production questionnaire. See the packages, or read our guide on how to get 12 testers.