12 Testers 14 Days / The testing guide
How Google Play
closed testing works.
Prepare your Android build, invite eligible testers, follow the 14-day window, and turn feedback into a stronger production-access application.
Explore testing plans Walk through the process ↓The closed-testing baseline
A continuous testing window
Your brief, updates, and report
Your route to launch
One step at a time.
Everything in view.
Prepare the app. Coordinate the test. Use what you learn.
See a sample report- 01
Prepare
Tell us what you’re building.
Choose a testing plan and submit your app link, access instructions, and the journeys you want tested. Include any login details testers will need.
A clear brief before testing begins - 02
Connect
Get your testing group ready.
Follow the setup instructions for your closed test. Keep the build available and resolve access questions so testers can reach the right version of your app.
An accessible build and a shared starting point - 03
Follow along
Keep the test moving.
Use your workspace to follow progress, check updates, and answer questions during the testing window. Share changes when you publish a new build.
Updates and conversations in one place - 04
Review
Turn the findings into next steps.
Read your closeout report, review the observations, and decide what to fix before applying for production access in Play Console.
A useful record for your next release decision
Before you begin
A little preparation.
A smoother test.
Have these details ready when you submit your app. Clear instructions help testers spend their time on the experience that matters.
- Your Android app name and closed-test link
- Working sign-in details for any restricted screens
- The main tasks you want testers to try
- Known issues and anything that needs special attention
Ready when your build is
Give your next release
a proper test run.
Managed testing: $15 for one app run or $29 for two. Review the plan details before you start. Your team makes the final submission; Google decides production access.