How to Create a Closed Testing Track in Play Console, Step by Step

To create a closed testing track, open your app in Play Console, go to the closed testing page under Test and release, create or pick a track, add testers, upload a signed app bundle, and roll it out. The steps are short, but a few small mistakes can quietly stop your testers from getting the app. This guide covers the whole process in order.

Play Console's layout and wording change from time to time. If a menu name here doesn't match what you see, check the official page, Set up an open, closed, or internal test, in Play Console Help.

Before you start

Have these ready so you don't stall halfway through:

A signed Android App Bundle (.aab) built in release mode. Play requires bundles for new apps.
A unique version code. Each upload to any track needs a version code higher than anything you've uploaded before.
An app already created in Play Console with a name, default language, and app type.
A list of tester email addresses, or a Google Group that contains them. Testers must use the Google account that is signed in to Play Store on their device.

If you have a personal developer account created after November 13, 2023, you'll need to run a closed test before applying for production access. The requirement is currently 12 testers opted in for 14 days in a row. It started at 20 testers. For the full rules, see the FAQ.

Step 1: Open the closed testing page

Sign in to Play Console and select your app.
In the left menu, open Test and release, then Testing.
Choose Closed testing.

You'll usually see a default track, often named something like "Closed testing - Alpha". You can use it as is. If you want a separate group, for example one for friends and one for a paid tester pool, you can create an additional track.

Creating a new track

Click Create track and give it a name. The name is for your own organization only, so make it descriptive, such as "Beta - Android 14 devices". Testers don't pick between tracks. They only see the opt-in link you send them.

Step 2: Add your testers

Open the track and go to the Testers tab. You have two main options.

Email list: create a list, name it, and paste in addresses separated by commas or one per line. You can also upload a CSV.
Google Groups: enter the group's email address. This is easier to manage when your testers change, because you edit the group instead of the track.

Tick the checkbox next to each list or group you want active on this track. A list that exists but isn't ticked does nothing, and that's an easy thing to miss.

Add a feedback channel

On the same tab, there is a field for a feedback email address or URL. Fill it in. It's where testers are pointed to send comments, and it saves you from guessing why someone uninstalled.

Step 3: Choose countries and regions

Open the Countries/regions tab and add the places where your testers live. A tester in a country you didn't select may not be able to install the app, even with a valid opt-in. If your testers are spread across several countries, add all of them. You can change the list later.

Step 4: Create the release

Go to the Releases tab of the track and click Create new release.
If prompted, set up Play App Signing. For a new app, letting Google manage the app signing key is the standard route.
Upload your .aab file. Wait for processing to finish.
Check the release name. Play fills in a default from your version, and you can edit it.
Write release notes, at least a short line like "First closed test build". Testers may see them.
Click Next.

Play Console will then show any errors or warnings for the release. Errors block the rollout, while warnings usually don't. Common blockers are a duplicate version code, a missing declaration, or an unfinished setup task in the dashboard. Which tasks are required before a test release can vary, so follow whatever Play Console lists for your app.

Step 5: Roll out to the closed track

On the review screen, read the summary, then click Save and Start rollout to Closed testing (the exact wording and button position may differ). The release may go into review first. Review times vary, and a new app can take longer than an update.

Once it's approved, the track's status will show the release as available to testers.

Step 6: Share the opt-in link

Back on the Testers tab, find the How testers join your test section and copy the web link. Send it to your testers. Each tester should:

Open the link while signed in to the right Google account.
Tap Become a tester.
Use the link to open the app's Play Store page and install it.

Opting in alone isn't enough for your own records. Ask testers to actually install and open the app on a real Android phone. Remind them to stay opted in for the whole test period, since leaving can pull your count below the minimum.

Step 7: Check that it works yourself

Before you tell twelve people to install, do a dry run with your own account:

Add your own email to the tester list.
Open the opt-in link on a phone that isn't your build machine.
Confirm the app installs from Play Store, not as a sideloaded APK.
Open it and check that the main flow works.

It takes ten minutes and catches most problems: a missing country, an unticked list, or a crash on a fresh install.

Common problems

"Item not found" on the Play Store page. The release may still be in review, the tester used the wrong Google account, or the tester's country isn't on the list. Rollout and opt-in propagation can also take a while.
Tester can't see the opt-in page. They're probably signed in with a different account than the one on your list.
Update doesn't reach testers. A new upload needs a higher version code and has to be rolled out, not just saved as a draft.
Count looks too low. Testers who opt out reduce the number. Recruit a few more than the minimum so one dropout doesn't hurt.

Finding enough testers

Setting up the track is the easy part. Most small teams struggle to find twelve people who will stay opted in for two weeks. Friends and family are free but often forget, uninstall, or use iPhones. If you'd rather not chase people, TesterMob supplies real testers who use their own Android phones, spend about 20 minutes a day in your app, and send written feedback. The price is $9.99 per app, paid once in USDT, and you can see it on the pricing page. We're not affiliated with Google and can't guarantee that production access will be approved. What we can do is make sure the testing itself actually happens.

Quick checklist

Signed .aab with a new version code
Track created and testers list ticked
Feedback email or URL set
Countries/regions selected
Release rolled out, not just saved
Opt-in link tested on a second device
Testers told to stay opted in for the full 14 days

Once the track is live, the next job is keeping the testers active and reading their feedback. If you hit a wall during setup, get in touch and we'll try to point you in the right direction.