Setting Up Closed Testing in Play Console: A Real Walkthrough

The mechanics of closed testing aren't hard, but Play Console doesn't hold your hand, and a couple of small snags can eat an afternoon if you meet them unprepared. This is the walkthrough written the way you'd want a friend who's done it a few times to explain it.

Before you start

Have three things ready: a signed app bundle (an .aab, not an old-style APK), your app's basic store details filled in enough that Play Console will let you create a release, and a rough list of who your testers will be. If you're planning to use a Google Group for testers — and you should — create it before you begin so it's ready to attach.

1. Create the closed testing track

In Play Console, open your app and go to Testing → Closed testing. You'll usually find a default track already there; you can use it or create a new one. Open the track and start a new release.

2. Upload your build and roll it out

Upload your .aab to the release, add short release notes, and save. Then actually roll the release out — this is the step people skip. A release that's saved as a draft but never rolled out won't be installable, and your opt-in link will look broken to testers even though everything 'looks' set up. Roll it out to the track before you share anything.

3. Add your testers

On the track's testers tab you can add people two ways: paste a list of email addresses, or point the track at a Google Group. Use the Group. Over a two-week test you will add and remove people, and editing a Group's membership is instant, whereas re-saving an email list on the track each time is tedious and error-prone. Add every tester's Google account — the one they'll actually install with.

4. Share the opt-in link

Each track has a web opt-in URL. Copy it and send it to your testers. Each person has to open that link, accept the invitation to test, and then install your app from the Play listing that the link leads to. Only after they've done all three do they count as opted in.

The gotchas worth knowing in advance

• Testers must use the exact Google account you added — a different account on the same phone simply won't see the test.
• Opt-in and availability can take a little while to propagate after you roll out; if the link seems dead immediately, wait a bit before assuming something's wrong.
• A saved-but-not-rolled-out release is the single most common reason the whole thing appears broken.
• On some devices testers need to be signed into Play with the right account and may have to clear the Play Store cache before the test build appears.

Managing the two weeks

Once people are opted in, your job shifts from setup to maintenance: keep the opted-in count at twelve or above, every day, for fourteen continuous days. Watch for drop-offs and have a few spare testers ready to backfill so a single person losing interest doesn't break your streak. This ongoing reliability is the genuinely hard part — and it's the reason CloseTesting exists. We supply verified testers who stay for the window and replace anyone who drops, so the count you set up on day one is still there on day fourteen.