Google Play Closed Testing Checklist: From Zero to Production

Before you start (day -3 to day 0)

• Create the closed testing track in Play Console and upload the build you want tested: internal testing does not count for this requirement.
• Prepare a list of 14-16 testers, not exactly 12, so one dropout does not put you below.
• Add their Google emails to the test list and share the opt-in link: Google does not notify anyone for you.
• Ask each tester to accept the link with the same account you added and install the app from Play Store.

During the 14 days

• Check the Play Console counter regularly: it is the source of truth, more than any estimate from us or anyone else.
• Ask testers to use the app on several days and cover the main flows; the production form asks about real usage.
• If someone drops out, replace them quickly: each tester's 14 days must be consecutive.
• Note the bugs they find and fix them: you will describe this in the form later.

At the end: request production

• Request production access only once the 12 required testers have completed 14 consecutive days opted in.
• Answer the questionnaire with real data: how many testers, what they tested, what you fixed.
• Be ready for Google to reject it: approval is not guaranteed; if it happens, review the causes and fix them before asking again.

Common mistakes

• Staying at exactly 12 testers with no margin.
• Testers who never opened the opt-in link with the right account.
• Using internal testing thinking it counts.
• Assuming an app update does not affect the counter without checking Play Console.

If you do not have 12 testers

You can cover the quota with your community, with freelancers or with a marketplace such as Tester Marketplace, which provides real testers and measurable usage. We cannot guarantee Google will grant access: we provide the testers and the data for the form.