How to Set Up Closed Testing in Google Play Console

This guide walks through closed testing in Google Play Console from an empty track to a working opt-in link. Every step comes from Google's Help Center articles Set up an open, closed, or internal test and Prepare and roll out a release. Play Console menus can change over time; where they differ from what you see, Google's articles are the reference.

The menu paths below use the names Google gives in its documentation, such as Test and release > Testing > Closed testing.

Before you start

Three things need to be true before the steps below will work:

• Your app setup is complete. Google lists this as the requirement for the closed testing track. Internal testing, by contrast, can start before setup is complete.
• You have the permission to release. Creating a new release needs the Release apps to testing tracks account permission.
• Your testers have Google accounts. Users need a Google Account or a Google Workspace account to join a test.

If you have a personal account created after November 13, 2023, this closed test is also what unlocks production. Our guide to closed testing requirements explains who that applies to.

Step 1: Open the closed testing track

Sign in to Play Console, select your app and go to the Closed testing page (Test and release > Testing > Closed testing). Google explains that a closed testing track is already available on this page as your initial closed test.

Click Manage track to configure it. If you need more than one closed test, for example for different teams or features, click Create track near the top right, enter a track name and click Create track. Google notes that you can run multiple closed tests and one open test at the same time. Additional closed tracks do not support some features, including country targeting.

Step 2: Add testers with an email list

Email lists are the default way to choose who can join. Google's steps are:

1. On the closed testing page, click Manage track.
2. Select the Testers tab.
3. Under 'Testers', click Create email list.
4. Enter a list name. You can reuse the same list for future tests on any of your apps.
5. Add email addresses separated by commas, or click Upload CSV file.
6. Click Save changes, then click Create.

Two rules about CSV uploads are easy to miss: uploading a CSV file overwrites any email addresses you previously added, and Play Console does not accept CSV files saved as UTF-8 with BOM. For size, Google allows up to 200 lists, each with up to 2,000 users, and up to 50 lists per track.

Back in the 'Testers' section, make sure Email is selected and tick the lists that should test this release.

Step 3: Or add testers with a Google Group

Instead of email lists, you can point the track at a Google Group. In the 'Testers' section select Google Groups and enter the group's email address in the format yourgroupname@googlegroups.com. Google explains that only members of the specified groups can join your test.

The important difference is the order of events for your testers: for closed tests that use a Google Group, users must join the group before they can opt in to your test. If someone opts in first, they will not get access.

Add testers by organization (managed Google Play)

A closed test can also be opened to an organization rather than to individual people. Google explains that you choose which organization can access your track, and admins of that organization then assign users to test your release. Google recommends adding testers either through Play Console or from the Android app settings page in the Google Admin console. If a user is selected to test from both, they receive the highest version code among all available app versions.

Before you can add testers associated with an organization that uses managed Google Play, go to the Managed Google Play tab on your app's Advanced settings page (Test and release > Advanced settings) and select the Turn on checkbox. Google warns that this makes the app private, which means it is no longer searchable on the public Play Store. If your app is private, you must also add the organization associated with your test to your targeted list.

To add an organization to a closed test, Google's steps are:

1. On the closed testing page, click Manage track.
2. Select the Testers tab.
3. In the 'Manage organizations' section, click Add organization.
4. Enter the ID and name of the organization that can access your track.
5. Click Add, then click Save changes.

Google notes that an organization ID is created automatically when an organization sets up Android management with access to Managed Google Play. Additional closed tracks don't support enterprise targeting used to publish private apps.

Step 4: Add a feedback channel

On the same Testers tab, provide a feedback URL or email address. Google says your feedback channel appears on the tester opt-in page, so it is the first place testers will look when they want to report something.

This matters more than it seems. Testers cannot leave public reviews on Google Play for test versions, so a direct channel such as email, a website or a forum is how you will hear about problems. In open and closed tests, testers can also send private feedback through Google Play.

Step 5: Create and roll out a release

A track with testers but no release gives them nothing to install. Google's release steps are:

1. On the closed testing page, click Manage track, then Create new release near the top right. If that button is disabled, complete any outstanding setup tasks listed on your Dashboard.
2. Follow the on-screen instructions. On your first release for the app, configure Play App Signing.
3. Add your app bundles, either by uploading them or with Add from library.
4. Name the release and enter release notes. Google allows up to 500 Unicode characters per language.
5. Click Next. If an 'Errors summary' appears, resolve the problems: you cannot publish until errors are fixed.
6. Click Start rollout.

Depending on whether your changes need review, Play Console shows options to Save or Publish. Saved changes go to the Publishing overview page, where you decide when to send them for review.

Step 6: Share the opt-in link

Back on the Testers tab, copy the shareable link and click Save changes. This opt-in link is how testers join. Before an open test or production release, closed testers cannot find your app by searching Google Play, so the link is the way in.

Keep three facts from Google in mind:

• The opt-in link displays only when the app status is 'Published'. Apps in 'Draft' or 'Pending publication' status do not show it.
• After you publish a test for the first time, the link can take several hours to become available to testers. Later changes can also take several hours.
• After clicking the link, testers see an explanation of tester responsibilities and a link to opt in. Each tester must opt in themselves.

If this test is for the production requirement, remind testers that they need to stay opted in continuously. Our guide to 12 testers for 14 days explains why.

Step 7: Collect and review feedback

Once testers install your app, Google says their app updates to the test version automatically within a few minutes. To read private feedback in Play Console, go to the Testing feedback page (Monitor and improve > Ratings and reviews > Testing feedback). You can filter by date, language, reply state, app version or device type, or search for keywords.

Google recommends keeping a record of the feedback you receive. If you are applying for production access, you will need to summarize that feedback in the application.

Testing feedback notifications

Google's article View and analyze your app's ratings and reviews covers the Testing feedback page in more detail. If you have an app in testing, you can access and reply to user feedback in Play Console, and Google states that this beta feedback is only visible to you and can't be seen on Google Play.

You don't have to check the page by hand. Google says you can set up your notification preferences to receive email notifications when users write new reviews, update existing reviews or submit new testing feedback. During a closed test that runs for 14 days, an email for each new piece of feedback makes it easier to reply while the tester still remembers what happened.

Paid apps and license testing

Paid apps follow different rules on each track. Google states that testers must purchase paid apps when they take part in open or closed tests, while internal testers can install paid apps for free. Internal testers still pay for in-app purchases unless you add them to a license testers list. Changes to your app's pricing affect all versions across all tracks.

License testing is how you test in-app billing and subscriptions without charging testers. Google's article Test in-app billing with application licensing explains the setup:

1. Open Play Console and click Settings > License testing.
2. Choose license testers with email lists or Google Groups. Each email list can contain up to 2,000 email addresses. With Google Groups, all members of the group are license testers, and Google notes that groups do not have a user limit.
3. Click Save changes.

Your own publishing account is always considered a licensed tester. Before testing, Google says your app must be published to the open, closed, internal test or production track (it recommends the internal test track), your testers must be eligible to receive that release, and your one-time products and subscriptions must be published. Once application licensing is set up, authorized users can purchase one-time products and subscriptions without charging their accounts.

Setup problems to check first

• Testers can't see the closed test. Check whether they are opted in to your internal test. Google notes that internal testers are not eligible for closed or open tests until they opt out of the internal test.
• No opt-in link. Check that the app status is 'Published' and allow several hours after the first publication.
• Create new release is greyed out. Complete the setup tasks listed on your Dashboard.
• Paid app. Google notes that testers must purchase paid apps in open or closed tests.
• Country availability. Changes to distributed countries and regions apply across all tracks.

Frequently asked questions