How to Publish a Closed-Test App on TestCrew

Before publishing an app on TestCrew, configure the shared testcrew-closed Google Group as an eligible tester group in Google Play Console and publish the closed-test release.

In the current TestCrew flow, you normally submit the standard Google Play Store details URL rather than a separate opt-in URL.

The four publication steps

1. Add testcrew-closed@googlegroups.com as an eligible Google Group for the closed-testing track
2. Publish the closed-test release
3. Register the standard Play Store details URL in TestCrew, such as https://play.google.com/store/apps/details?id=...
4. Complete TestCrew’s pre-publication checks

Creating the listing before the group and release are ready will not allow testers to participate.

What happens immediately after submission

A newly submitted listing enters a pre-publication checking state. Eligible TestCrew users attempt to access the app and verify participation, installation, and basic operation.

Under the current service design described in the app:

• A tester who completes the pre-publication check may receive an additional credit beyond the normal reward
• A listing may be published early after the required checks are satisfied
• If the early-publication condition is not reached within 24 hours, the listing may still be published automatically when no serious problem has been reported
• Repeated or significant problem reports may suspend the listing until it is corrected

While the check is in progress, the listing is not shown as a normal recruitment listing until the required decision is complete. Confirm the current in-app rules because detailed conditions can change.

Required state before listing

Confirm all of the following:

• The app has been created in Play Console
• A closed-testing track exists
• testcrew-closed@googlegroups.com is configured as an eligible tester group
• An AAB has been published to the target track
• The standard Play Store details URL has been verified
• The app has been checked with an account that belongs to the testcrew-closed group
• The app can be installed and launched

When Play Console setup is incomplete, start with How to Set Up a Closed Test in Google Play Console.

Information to prepare

App name

Use a name that corresponds to the Google Play listing. A private development codename alone makes it difficult for participants to identify the app.

App description

Do not paste the entire store description. Summarize the purpose and requested test scope.

This Android app saves photos and notes by date.
For this test, please check registration, photo saving, and history display.

Play Store details URL

Use the standard app details page URL expected by the current TestCrew flow.

https://play.google.com/store/apps/details?id=com.example.app

After entering the URL, confirm that:

• It opens the correct app’s Play Store details page
• It is opened with an account that has joined the testcrew-closed Google Group
• The app can be installed

Features to check

Limit the list to approximately three to five items.

1. Create a new account
2. Sign in
3. Save one photo
4. Open the saved history
5. Restart the app and confirm the data remains

Eligibility conditions

State relevant conditions such as:

• Supported Android versions
• Target country and language
• Tablet support
• Required Google or other account
• Special device features

Cautions

Explain conditions such as:

• Remain opted in for 14 days
• Use test data
• Do not make a real purchase
• Do not enter unnecessary personal information
• Report problems through the specified channel

Example listing text

I am recruiting closed testers for an Android app that organizes photos and notes.

Please check:
- Registration and sign-in
- Saving one photo
- Opening the saved history
- Data after restarting the app

After joining, install the app from Google Play and remain opted in for 14 days.
If you find a problem, share the device model, Android version, and reproduction steps.

Self-test before publication

Test with a separate tester account rather than only the developer account.

1. Open the Play Store details URL you plan to submit
2. Confirm that the account has joined the testcrew-closed Google Group
3. Install the app
4. Launch it for the first time
5. Complete the requested actions
6. Confirm that the account can receive an updated build

A developer device may still have a debug build installed. When possible, use a separate device, Android user, or clean tester environment.

Areas where participants often get stuck

Google account selection

When a participant has multiple accounts, ask them to confirm which account joined the tester group and which account is active in the Play Store.

Test sign-in information

If the app requires sign-in, state whether testers should create their own account or use a provided test account.

Permissions

Explain why the app requests access to photos, notifications, location, or other device capabilities.

Completion conditions

Clarify whether completion means installation only or whether the tester must use specified features and submit a report.

What to do after publication

• Respond to reports that testers cannot participate
• Monitor tester counts in Play Console
• Record feedback
• Fix defects
• Increase the versionCode and publish updates
• Tell participants what changed
• Monitor return-testing status

When URLs or tester settings change

After changing the track or tester configuration, verify that the published listing still points to a working participation path.

Leaving an obsolete configuration in place can cause participants to enter the wrong track or see an ineligible-app message.

When to pause recruitment

Consider pausing the listing when:

• The required participant count has been reached
• A serious defect has been found
• Users cannot sign in
• A new AAB is being prepared
• The Google Group configuration is no longer valid
• You cannot keep up with participant support

A stable experience for existing testers is more important than continuing to recruit while the app is unusable.

Summary

Publish on TestCrew in this order:

1. Publish the closed test in Play Console
2. Verify the testcrew-closed Google Group and release configuration
3. Test the standard Play Store details URL from a tester’s account
4. Prepare a clear app description and test checklist
5. Submit the TestCrew listing
6. Respond to pre-publication checks and participation problems
7. Apply feedback to app improvements

Participant instructions can link to How to Join a Test as a TestCrew Tester.