Testing guides / Closed testing planner
Plan your 14-day
Google Play closed test.
Use the date your twelfth tester opts in to plan the earliest time you may be able to apply for production access. Your Play Console remains the source of truth.
When could I apply?
Choose a date to see the planning window.
This adds 14 calendar days for planning only. Testers must remain opted in continuously, and Google separately reviews your production-access application.
Pre-flight checklist
- My app is in the closed testing track, not internal or open testing.
- My tester emails or Google Group have been added in Play Console.
- My opt-in link works for the intended tester accounts.
- My app installs and opens on an Android device.
- I have a short list of features or journeys for testers to try.
- I have a way to record feedback, fixes and retest notes.
If a tester opts out, their qualifying period is interrupted. Review your own Play Console before applying.
What to track during the 14 days
Keep a simple dated record of the build being tested, opt-in or access issues, feedback received, changes made and any retesting. These notes help you explain the real testing process if Google asks about your production readiness.
For the full policy context, read our Google Play testing requirements guide. For a managed group, see 12 testers for 14 days.
Need help coordinating the test?
Stop chasing testers yourself. Gigsdo provides 12 real Android testers for the agreed 14-day closed test, with app feedback and a testing-fee refund if the completed test is not approved.
Get 12 testers today