How to Set Up a Google Play Closed Test in Play Console

A Google Play closed test requires three connected settings in Play Console:

1. A closed-testing track
2. The testers who are allowed to participate
3. A release that those testers can install

Configuring only one of these is not enough. A tester list without a published AAB cannot install anything, and a published AAB is unavailable to someone who is not eligible to opt in.

Before you begin

Confirm that:

• The app has been created in Play Console
• The package name is final
• A release AAB has been generated
• The versionCode has not been used before
• The required store listing and app-content information has been entered
• You know which Google accounts the testers will use

When the AAB cannot be uploaded, check App Bundle Upload Error first.

Step 1: Open closed testing

Select the app in Play Console and open the closed-testing area from the testing and release menus.

Play Console labels can change. If the wording does not exactly match this guide, look for menu items related to “Testing” and “Closed testing.”

Step 2: Create a track

Set a track name when necessary.

Examples:

alpha
closed-test
production-access-test

The track name is mainly for the developer to distinguish multiple tests. It is not the explanation shown to testers.

Avoid creating too many tracks

Creating several closed tests for the same purpose can cause problems:

• The wrong participation link is shared
• versionCode priority becomes difficult to understand
• Testers join different tracks
• Tester count and duration become harder to monitor

For a production-access test, managing participants in one closed-testing track is usually simpler.

Step 3: Configure testers

Use the tester-management method supported by Play Console, such as an email list or Google Group.

When using an email list

Register the email address of the Google account that the tester will actually use.

Registered email
= account used to open the participation link
= account selected in the Play Store

The most common problem is not letter casing but an incorrect address or a different Google account.

Tell testers in advance

• Which Google account was registered
• That opt-in is required
• That the app must be installed from Google Play
• That they should not leave the test for 14 days
• Which features they should check

Step 4: Create the release

Create a new release in the selected track and upload the AAB.

Check:

• The package name matches the Play Console app
• The versionCode is appropriately higher than previous uploads
• The bundle is signed for release
• The AAB was built for the intended environment
• Debug URLs or development API keys are not included

Step 5: Write release notes

Release notes should tell testers what changed and what they should verify.

This is the first closed-test release.
Please test registration, sign-in, photo saving, and history display.
If you find a problem, share the device model, Android version, and reproduction steps.

For an updated build, describe the fixes specifically.

- Improved the error shown after a failed sign-in
- Added a completion message after saving a photo
- Fixed the layout on smaller screens

Step 6: Review warnings and errors

Distinguish the messages shown during release creation:

• Error: must be resolved before publishing
• Warning: review the details and respond when necessary
• Information: use it when deciding whether the release is ready

Do not dismiss messages mechanically. Check whether they concern APIs, permissions, signing, or the App Bundle.

Step 7: Publish the release

Saving a release does not distribute it to testers. Complete all steps shown for review, publication, or rollout.

Processing may continue for some time after submission.

Confirm that the release is

• Not a draft
• Not waiting for a required submission step
• Not blocked by an error
• Available in the intended track

Step 8: Obtain and test the opt-in URL

Copy the participation link and test it yourself with a tester account before sharing it broadly.

1. Open the link with the eligible account
2. Confirm that the test participation page appears
3. Complete the opt-in action
4. Continue to the Play Store listing
5. Install the app
6. Launch the latest version

Step 9: Send instructions to testers

Share the following information:

Participation link:
Registered Google account:
Features to test:
How to report feedback:
Required participation period:

When listing the app on TestCrew, see How to Publish Your App on TestCrew.

Managing the test after publication

Tester count

Track each participant’s opt-in and installation report in addition to the count shown in Play Console.

Feedback

Record the issue, device, reproduction steps, and current resolution status.

Updates

When publishing a corrected build, increase the versionCode and release it to the same track.

Participation status

Check whether any tester has left during the required period.

Common mistakes

• Assuming that adding someone to the tester list completes participation
• Leaving the release as a draft
• Sharing an internal-testing URL instead of the closed-test URL
• Publishing an opt-in link for another app
• Allowing a debug build and Play build to conflict on the device
• Reusing the same versionCode
• Failing to tell participants what to test

Summary

Set up a closed test in this order:

1. Create the track
2. Configure testers
3. Create a release with the AAB
4. Review warnings and errors
5. Publish the release
6. Verify the opt-in URL
7. Send instructions to testers
8. Track tester count, duration, and feedback

For participant-facing instructions, share How to Participate as a TestCrew Tester and What Testers Should Do During the 14-Day Closed Test.