How to Setup Closed Testing in Google Play Console (Step-by-Step)

Navigating the Google Play Console UI can sometimes feel more complicated than actually programming your app. Menus are hidden inside sub-menus, warnings pop up without context, and making one wrong click can delay your launch by a week.

If you have built your App Bundle and you are ready to tackle the 14 days closed testing rule, you need to set up your track perfectly. A single mistake here—like forgetting to enable certain countries or grabbing the wrong opt-in link—will result in your testers seeing a "404 Not Found" error.

In this guide, we are going to walk you through the exact step-by-step process of setting up closed testing in the Play Console, adding your testers, and extracting the right link to share.

Step 1: Prerequisites & Store Listing

Before you even click on "Testing," you need to have a few things ready. Google will not let you roll out a closed test if your basic app foundation is missing.

• App Bundle: You must have a signed .aab (Android App Bundle) generated from Android Studio or your framework of choice.
• Main Store Listing: You need an app icon, a short description, a full description, and at least two screenshots uploaded.
• Privacy Policy: You must have a URL pointing to a valid privacy policy in the App Content section.

Step 2: Navigating to the Closed Testing Track

Once your app foundation is set, follow these steps to reach the correct track. (Remember, do not confuse this with the Internal track. If you are unsure, read our guide on internal vs closed testing).

1. Log into the Google Play Console.
2. Select your application from the dashboard.
3. Look at the left-hand navigation menu. Scroll down to the Release section.
4. Click on Testing to expand the drop-down.
5. Click on Closed testing.

Step 3: Creating an Alpha Track

By default, Google provides an "Alpha" track. You can just use this one, or you can create a custom track if you want to run multiple tests simultaneously.

1. On the Closed testing page, click on Manage track next to the Alpha track.
2. If you prefer to make a new one, click Create track in the top right, name it (e.g., "14 Day Launch Test"), and click Create.

Step 4: Setting Up Your Testers (Crucial Step)

This is where most developers make a mistake. You need to tell Google exactly who is allowed to download this app.

1. Inside your chosen track, click on the Testers tab.
2. You have two options for managing testers: Email lists or Google Groups.

Option A: Email Lists (Best for small, manual lists)

If you personally know the 12 people testing your app, you can create a list. Click "Create email list," give it a name, and paste in the 12 Gmail addresses separated by commas. Save the list, and make sure the checkbox next to it is selected.

Option B: Google Groups (Best for Reddit/Discord sourcing)

If you are trying to find 12 testers organically online, maintaining an email list is a nightmare. Instead, create a free Google Group. Copy the email address of that Google Group (e.g., my-app-testers@googlegroups.com) and paste it into the Play Console under the Google Groups section. Anyone who joins that group automatically gains testing permission.

Step 5: Country / Region Availability

If you skip this step, your testers will get an error saying the app is not available in their country.

1. Still inside your track management, click on the Countries / regions tab.
2. Click Add countries / regions.
3. Unless your app is legally restricted to a specific country (like a local banking app), click the top checkbox to select All countries and regions.
4. Click Save.

Step 6: Creating the Release and Uploading the Bundle

Now you actually need to give the testers something to download.

1. Click on the Releases tab within your track.
2. Click Create new release.
3. In the "App bundles" section, upload your .aab file.
4. Give the release a name (e.g., "Version 1.0 Alpha").
5. Add some release notes. (This is good practice for when you eventually submit your production access questionnaire).
6. Click Next, review the release, and then click Save and publish (or Start Rollout to Closed Testing).

Step 7: Getting Your Opt-In Link

Once your release is approved and active, you need to send a specific link to your testers. Do not send them a link to the public Play Store.

1. Go back to the Testers tab inside your closed testing track.
2. Scroll down to the bottom of the page. You will see a section titled "How testers join your test".
3. You will see two links: "Join on Android" and "Join on Web."
4. Copy the Join on Web link. This is the link you send to your testers. When they click it, they will be prompted to log into their Google account and click an "Accept Invitation" button.

The Easiest Way to Fill Your Track

You have successfully set up the console, uploaded the app, and generated the link. Now comes the hard part: getting 12 real people to actually click it and keep the app installed for 14 days without breaking the streak.

If you don't want to spend the next two weeks hunting for reliable people, let 12 Testers Hub handle it. You simply provide us with that "Join on Web" opt-in link you just generated. Our network of real Android devices will join your test, download the app, and provide the guaranteed engagement required by Google policy.