Google Play Closed Testing Checklist: Before, During and After the 14 Days
Everything to do before you start your closed test, while it runs, and before you apply for production access, in one checklist.
Before
Set up right
During
Keep 12+, collect feedback
After
Apply with real answers
Before the test starts
Your app
- The core feature works end to end on a fresh install.
- No placeholder text, test buttons or debug screens.
- A signed Android App Bundle (.aab) with a new version code.
- A privacy policy URL that describes what the app actually does.
Play Console
- App created, and the dashboard's setup tasks finished: app access, ads, content rating, target audience, data safety.
- Store listing done properly. Testers see it on the opt-in page.
- A closed testing track, not internal. Here's the difference.
- Countries / regions include every tester's country.
- A feedback URL or email on the Testers tab.
- A release approved and live on the closed track.
Need the details? See how to set up a closed test step by step.
Testers
- 15 or more testers lined up, not exactly 12. Here's why.
- Each tester's exact Google account: the one on their phone's Play Store.
- Added as an email list or Google Group (group members have accepted their invites).
- A short message with the opt-in link, what to do, and the end date.
During the 14 days
- Every 2–3 days: check the tester count in Play Console. Still 12 or more?
- If someone drops out: replace them the same day.
- Around day 5 and day 10: send testers a reminder and something specific to try.
- Collect feedback in one place (a form, a chat, a sheet) as it comes in.
- Ship at least one update that fixes what testers reported.
- Watch Android vitals for crashes and ANRs.
- Keep notes: bugs found, versions released, devices used. You'll need them soon.
Before you apply for production
- 14 days in a row with 12 or more testers opted in. Check the whole window.
- Every reported bug fixed or explained.
- No open policy warnings in Play Console.
- Your notes ready for the questions: how you recruited, how testers engaged, what feedback you got, what you changed and why you think it's ready.
Then answer the production access questions with specifics. If it doesn't go through, here's why applications get rejected and how to fix it.
FAQ
When do the 14 days start?
From the first day you have 12 or more testers opted in to your closed test. Keep the count at 12 or more every day after that.
Can I update my app during the closed test?
Yes, and you should. Shipping fixes based on tester feedback is exactly what Google wants to see, and it gives you something concrete for your production access answers.
Do I need a privacy policy for a closed test?
Play Console asks for a privacy policy as part of your app setup, so have one ready before you start.
What should I keep notes on during the test?
How you recruited testers, how many stayed, the bugs and feedback they reported, the updates you shipped, and the devices and Android versions used.

Talk to a human, not a bot
Stuck on setup, Google's rules or your app? Message us and a real person from our team answers.
- Avg. reply under 5 minutes
- Any day of the week
Keep reading
- Closed vs Internal vs Open Testing on Google Play: What's the Difference?Google Play has three testing tracks. Here's who each one is for, how testers join, and which one counts for the 12-tester requirement on new personal accounts.
- Free vs Paid Google Play Testers: An Honest ComparisonFriends, tester exchanges, freelancers or a managed service? What each way of getting 12 Google Play testers really costs in money, time and risk.