Google Play Closed Testing:
Step-by-Step Setup for New Developers

Prerequisites: What you need before you start

If you try to set up an android app closed beta setup without having these items ready, you will get stuck halfway through the Google Play Console menus. Ensure you have the following:

• A Google Play Developer Account: Fully verified with your identity and payment completed.
• Your App Dashboard Completed: You must have finished the initial "Set up your app" tasks (Privacy policy, App content ratings, Target audience, Data safety form, etc.).
• An App Bundle (.aab file): Your compiled, signed Android App Bundle ready to upload. Do not use an APK.
• Your Testers' Emails: If you already have your 12 testers, have their Google-associated email addresses ready in a text file or CSV. (If you don't have testers yet, learn how to get them here).

Step 1: Navigate to the Testing section

Log into your Google Play Console and select the app you want to test from the "All apps" dashboard.

Look at the left-hand navigation sidebar. Scroll down until you find the Testing drop-down menu. You will see several options here, including Open testing, Closed testing, Internal testing, and Pre-registration. Click on Closed testing.

Step 2: Create a closed testing track

By default, Google Play provides an initial closed testing track called the "Alpha" track. For the vast majority of new developers, using this default Alpha track is perfectly fine for your 14-day requirement.

If you want to use the default track, simply click Manage track next to Alpha.

If you prefer to keep things organized differently (for example, if you are running multiple tests simultaneously), you can click the Create track button in the top right corner. Name it something memorable like "14-Day Production Test" and proceed.

Step 3: Create and roll out a release

Once you are inside your chosen closed testing track, you need to upload your actual app code so testers have something to download.

1. Click the blue Create new release button.
2. In the "App bundles" section, click Upload and select your compiled `.aab` file from your computer.
3. Wait for the file to process. Google will automatically fill in the Release name (e.g., `1.0.0`) based on your code.
4. Under "Release notes", type a brief description of what this version includes (e.g., "Initial beta release for core feature testing.").
5. Click Next at the bottom right.
6. Review the release. If there are any Errors (red icons), you must fix them in your code and re-upload. If there are only Warnings (yellow icons), you can usually ignore them for now.
7. Click Save and then Send for review.

Step 4: Set up your tester list

While you are waiting for the release to be reviewed, you can set up who is allowed to access the test. This is the core of the google play console testing track setup.

In your Closed testing track dashboard, click on the Testers tab (located next to the "Releases" tab).

You have two options to add testers:

• Email lists (Recommended): Click "Create email list." Name the list (e.g., "14 Day Testers"). You can manually type in the Gmail addresses of your testers, separated by commas, or upload a `.csv` file. Once added, ensure the checkbox next to your new list is selected.
• Google Groups: Alternatively, you can paste the email address of a Google Group. Anyone who joins that Google Group will automatically be granted testing access.

Scroll down to the bottom of the Testers page and click Save.

Step 5: Copy and share the opt-in link

Once your app release has been reviewed and approved by Google (status will say "Available"), return to the Testers tab in your Closed testing track.

Scroll down to the "How testers join your test" section. You will see two links:

1. Join on Android: A link that only works if clicked from an Android device.
2. Join on the Web: A standard web link (e.g., `https://play.google.com/apps/testing/com.yourpackage.name`).

Always share the "Join on the Web" link. It is much more reliable. Your testers will click this link, sign into their Google account, and click a button that says "Become a tester". After doing that, they will be given a link to download the app directly from the Play Store on their phone.

The moment 12 unique accounts click that opt-in button, your 14-day clock begins! (Read more about the fastest way to get production access once the clock starts).

Internal vs Closed testing: What's the difference?

Many new developers accidentally set up an Internal testing track, invite 12 people, wait 14 days, and then realize it didn't count toward the Google Play requirement. Understanding the difference is critical to an effective google play closed testing track setup.