Step-by-Step: Create a Closed Testing Track & Invite Testers in Play Console

Before you start, make sure you have a fully verified Google Play Developer account and have uploaded at least one signed app bundle (AAB) to the Play Console. You should also have a list of tester emails or a Google Group ready to manage them. Having all of this in place makes the following steps go smoothly.

In the Play Console, open your app and go to Testing → Closed testing. Click "Create track" to make a new track (or use the existing "Alpha" track). Give the track a recognizable name, such as "14-Day Closed Test," so it's easy to manage if you have multiple tracks later.

In the track you just created, find the "Testers" section. You have two ways to add them: paste a list of emails directly, or link a Google Group (recommended, since it's easier to add or remove people later). Make sure you have at least 12 testers — and as advised in earlier posts, add 2–3 extra for backup.

Note that each email must be a real, distinct Google account. This is a mandatory condition for Google to count a tester as valid.

Go to the track's "Releases" tab, click "Create new release," attach your app bundle and fill in release notes describing the version. After reviewing carefully, click "Review release" then "Start rollout to Closed testing." Google runs a review round on the build before it reaches testers — this step usually takes from a few hours to a few days.

Once the release is approved, the Play Console provides an "opt-in URL" (a join link). Send this link to all your testers. Each person must open the link, accept joining the testing program, then install the app from the Play Store via that same link. Only when they complete this step do they count as an opted-in tester.

Guide your testers clearly, because many aren't familiar with the opt-in process. A message with screenshots of each step significantly reduces the number who get it wrong or give up.

Once 12 testers have opted in, the 14-day clock starts. From here, your job is to check the dashboard daily to ensure the active tester count never drops below 12. If you notice someone going inactive, remind them immediately or activate a backup tester.

This is also the most tiring and risk-prone phase if you do it yourself. If you'd rather not spend 14 days monitoring and reminding, BetaBox can take over the whole thing: providing real testers, keeping them continuously active, and ensuring you reach the finish on time. You just provide the opt-in link and you're done.