How to create a closed testing track in Play Console, step by step

To create a closed test, open Test and release > Testing > Closed testing in Play Console, create or manage a track, choose countries, add testers, attach a release with your app bundle, and then send the changes for review from Publishing overview. Testers can only join once Google approves the changes and the track is published. Here is each step in order, with the details that usually cause delays.

Before you start

You can't use closed testing until app setup is complete (App testing requirements). That includes the App content declarations and the Data safety form. If any of those are still open, finish them first. Our pre-start checklist lists everything to have ready.

Also make sure you are on the right track. Internal testing is quicker to set up, but it doesn't count toward the 12-tester, 14-day requirement for new personal accounts. If you're not sure of the difference, see internal vs closed vs open testing.

Step 1: Open Closed testing

In Play Console, select your app. In the left menu, go to Test and release > Testing > Closed testing. Google sometimes renames or regroups menu items, so if you don't see this exact path, look for the "Testing" section in the menu.

Step 2: Create or manage a track

Play Console usually provides a default closed track (often named Closed testing - Alpha).

• If you see it, click Manage track.
• If you want a separate track, click Create track and give it a name you'll recognize.

One closed track is enough for the requirement. Extra tracks are useful later if you want different groups testing different builds, but they add complexity on your first test.

Step 3: Choose countries and regions

Open the Countries/regions tab of the track. By default, testing track availability is synced with your production countries. To set them separately, choose Unsync countries/regions, then Edit countries (Country distribution).

Include every country where your testers live. If a tester's country isn't selected, they likely won't be able to install the test. This is one of the easiest mistakes to miss because nothing warns you.

Step 4: Add testers

Open the Testers tab. You have two options (Set up a test):

• Email lists: create a list and add each tester's Google account email. You can have up to 200 lists per account, each with up to 2,000 users, and up to 50 lists per track.
• Google Groups: enter the group's address (for example [email protected]). Only members of the group can join.

Each tester needs a Google account or a Google Workspace account. Add the address they actually use on their Android phone. Also fill in the feedback channel (an email address or URL) if the form offers it, so testers know how to reach you.

Save your changes.

Step 5: Create a release

On the track page, create a new release.

1. Upload your Android App Bundle (AAB). On your first ever upload you'll also set up Play App Signing.
2. Check the release name Play Console suggests, or set your own.
3. Write short release notes so testers know what to try.
4. Save, then review the release. Fix any errors Play Console shows; warnings are worth reading too.

Uploading the bundle also triggers a free pre-launch report, which runs your app on test devices and usually returns results within an hour.

Step 6: Send the changes for review

This is the step people forget. Everything you've done so far is saved but not live. Go to Publishing overview. Your track, tester and country changes will appear as changes not yet sent for review. Click Send for review (the button text can vary slightly).

If you skip this, your testers see an error when they open the link, and your 14 days never start. This article explains the problem in detail.

Closed releases are reviewed by Google. Review can take a few hours or up to seven days, and longer in exceptional cases. New developer accounts may see longer reviews, so plan a buffer of at least a week (Managed publishing).

Step 7: Wait for "Published", then share the link

The opt-in link only appears when the app status is Published, not Draft or Pending. Even then, after you publish a test for the first time, the link "can take several hours to become available to testers."

When it's ready, go back to the Testers tab, copy the opt-in link and share it with your testers. Each tester opens the link, accepts the invitation, and installs the app from Google Play.

Quick recap

1. Test and release > Testing > Closed testing
2. Manage track or Create track
3. Countries/regions: include every tester's country
4. Testers: email list or Google Group
5. Create a release and upload the AAB
6. Publishing overview > Send for review
7. Wait for Published, then copy and share the opt-in link

Common problems

• "The link says the app isn't available." The change may not be sent or approved yet, or the first publish is still propagating.
• "A tester can't install." Check that their country is on the track and that they're signed in with the Google account you added.
• "Nothing happened after I saved." Saving is not publishing. Go to Publishing overview.

If you're using GoPlayTester, our step-by-step guide shows exactly which tester group to add and which country to include. Google decides on production access, but we supply 12+ real testers for the 14 days. You can order here.