A closed test is 14 days long, and most of the work is in the preparation and the checking. This plan breaks it into small steps. Google's actual requirements are few: at least 12 testers, opted in continuously for 14 days, then an application. The rest of this plan is a suggested routine, not a Google rule. The requirements come from Google's own help page.

Before day 1: preparation

• Finish your app setup. Google says you can start a closed test after completing it.
• Create the closed test and upload a build that works.
• Recruit more than 12 testers. A buffer of three or four is a good start.
• Prepare your instructions. Use our message template for testers.
• Prepare your feedback record.
• If your app needs a login, create a test account.

Day 1: everyone joins

• Send the message to all testers with the opt-in link.
• Check that testers are joining with the right Google account.
• Write down how many testers have opted in. This is your starting number.

Days 2 and 3: first check

• Count who has joined and installed. Remind those who have not.
• Read the first feedback and fix any blocking problem. Note it in your record.
• Send the day-3 reminder to stay opted in.

Days 4 to 6: feedback and fixes

• Check your feedback channel and the Testing feedback page in Play Console every day or two.
• Answer testers quickly. People who get answers stay involved.
• If someone has left, replace them now. See what to do when a tester drops out.

Day 7: halfway check

• Count opted-in testers again. Do you still have at least 12 who will reach 14 days?
• Review your record: which features did testers use, and which none touched?
• Send the day-7 reminder, and ask testers to try the features nobody has tried.

Days 8 to 11: keep it going

• Keep fixing and recording.
• Do not change your tester group unless someone leaves.

Day 12: the second reminder

• Send the day-12 reminder: please stay opted in until the end.
• Check the count again.

Day 13: before you apply

• Count testers who have been opted in for the preceding days. Use the free 12 tester calculator.
• Prepare your answers using the questionnaire guide.
• Fix anything serious. Google says the app must be stable and policy compliant, and that valid login credentials must be provided if the app needs a login.

Day 14 and after: apply

• When at least 12 testers have been opted in for the preceding 14 days, apply for production access on the Dashboard in Play Console.
• Our suggestion: do not remove testers right away. Keep the test running until you hear back.
• Google says the review usually takes seven days or less. If it asks you to continue testing, read what to do next.

If you want help

ClosedTest runs this routine with real testers, daily check-ins and a final report. See the pricing and the sample report. Google makes the decision on every application.

ClosedTest is an independent service and is not affiliated with Google.