How to Set Up a Closed Testing Track in Google Play Console: Step by Step

Setting up closed testing correctly is the foundation of a successful 14-day testing period. Errors in configuration - wrong tester group, missing opt-in URL, incorrectly uploaded release - cause testers to appear to join but not count toward your 12. Here is a complete step-by-step guide.

Before You Start: What You Need Ready

You need a Google Play Developer account ($25 registration fee, personal account created after November 2023 will require closed testing). You need a working APK or Android App Bundle (AAB) that installs on real devices without crashes. You need access to Play Console at play.google.com/console.

Step 1: Open Your App in Play Console

Log in to play.google.com/console and select your app from the dashboard. If you have not yet created an app listing, create one first by clicking Create app and completing the required store listing information.

Step 2: Navigate to Closed Testing

In the left sidebar, look for Testing. Expand it and select Closed testing. You will see the closed testing dashboard, which is initially empty.

Step 3: Create a New Release

Click Create new release. This opens the release configuration screen.

Step 4: Choose Your Signing Configuration

Google Play requires app signing. If this is your first release, you will be prompted to configure app signing. Accept Google Play's app signing (recommended) and follow the prompts. If you have an existing keystore, you can upload it.

Step 5: Upload Your APK or AAB

Drag and drop your APK or AAB file into the upload area, or click browse and select your file. Google recommends AAB format over APK as it enables better optimization for different device configurations.

Wait for the upload to complete and for Google to process the file. Processing typically takes a few minutes.

Step 6: Complete Release Information

Fill in the Release name field. This is an internal label for your reference - it does not appear to testers or users.

Write meaningful Release notes. These are visible to testers and are also a signal to Google that genuine testing is happening. Write notes that describe what this version includes and what you want testers to pay attention to. Do not leave this blank.

Step 7: Save and Go to Testers

Click Save at the bottom of the release screen. Do not click Review release yet.

In the left sidebar under Closed testing, click Testers. This is where you configure who can access your closed test.

Step 8: Create a Tester Group or Use an Existing One

Click Create email list and name your tester group. If you are using TestSlot, name it TestSlot Testers or similar.

Add the group email address. For TestSlot users, TestSlot provides a single group email address that you add here. This single action gives all TestSlot testers access to your app through the closed testing track.

Click Save.

Step 9: Enable the Tester Group for Your Release

Make sure your tester group is marked as included in your closed testing release. Go back to your release and ensure the tester group is selected.

Step 10: Publish the Release

Click Review release and then Start rollout to closed testing. Google will review your release. This typically takes a few hours.

Step 11: Copy Your Opt-In URL

After your release is published and under review, return to the Closed testing section. Look for the tester opt-in URL. Copy this URL. This is what your testers use to join your closed test.

If you are using TestSlot, paste this URL into your TestSlot listing when prompted. TestSlot uses this URL to give testers access to your closed test.

Step 12: Verify Tester Opt-Ins in Play Console

Once testers start joining, you can monitor them in the Testers section of your closed testing dashboard. You will see opted-in count, install count, and activity data.

The tester count that matters for the 14-day requirement is opted in and installed, not just opted in. Monitor both numbers.

Common Setup Errors to Avoid

Do not use the wrong email in the tester group. The group email you add must match exactly what your testing service provides. A single character error means testers cannot access your app.

Do not forget to publish the release. An unpublished or draft release is not accessible to testers.

Do not skip release notes. Blank release notes reduce the quality signals your testing sends to Google.

Configure correctly once and let TestSlot handle the rest at testslot.io.