How to Set Up a Closed Test in Google Play Console (Step by Step)

Before you start

You'll need:

• A Google Play developer account (one-time registration fee).
• Your app built as an Android App Bundle (.aab), signed and with a version code higher than any you've uploaded before.
• A privacy policy URL: Play Console asks for one in the app content section.
• Your testers' Google accounts, or a Google Group they're members of.

Prefer a single list to tick off? Use our closed testing checklist.

The path, end to end

1. 1Step 1

   Create the app

   Name, language, app or game, free or paid.

2. 2Step 2

   Finish app setup

   Store listing and app content declarations.

3. 3Step 3

   Set up the closed track

   Testers, countries, feedback channel.

4. Step 4

   Release and share

   Upload the .aab, get it reviewed, share the opt-in link.

Step 1: Create your app

In Play Console, click Create app and fill in:

• App name: you can change it later.
• Default language.
• App or game, and Free or paid. You can switch from paid to free later, but not from free to paid.
• Accept the declarations, then Create app.

Step 2: Finish the app setup tasks

Your app's dashboard lists setup tasks. Closed test releases can't go out for review until the required ones are done. Expect things like:

• App access: if parts of your app need a login, give Google test credentials.
• Ads: does the app show ads?
• Content rating: a short questionnaire.
• Target audience: age groups your app is for.
• Data safety: what data you collect and why.
• Privacy policy: the URL.
• Main store listing: short and full description, icon, feature graphic and screenshots.

Step 3: Set up your closed testing track

Go to Test and release → Testing → Closed testing. There's usually a default closed track already (often called Alpha); open it with Manage track, or create a new closed track.

Add your testers

Open the Testers tab and choose how testers are added:

Testers must use the same Google account that's signed in to Play Store on their phone, or they won't count.

Add a feedback channel

On the same tab, add a feedback URL or email address. Testers see it on the opt-in page, so they know where to report problems, and you'll want that feedback when you answer the production access questions.

Choose countries

Under Countries / regions, add every country your testers are in. A tester in a country you didn't select can't install the app.

Step 4: Create and roll out a release

1. On the closed track, click Create new release.
2. Upload your .aab file. If it's your first upload, Play Console sets up Play App Signing with you.
3. Add a release name (for example the version number) and release notes for testers.
4. Click Next, fix any errors it shows, then Save.
5. Go to Publishing overview and send the changes for review.

The first review of a new app can take a few days. Later updates are usually quicker.

Step 5: Share the opt-in link

When the release is approved and live on the track, go back to the Testers tab. Copy the opt-in link (it looks like https://play.google.com/apps/testing/your.package.name) and send it to your testers.

Each tester opens the link, taps Become a tester, then installs the app from Play Store. That's when they start counting towards your 12. There's a ready-to-send message in our guide to getting and sharing the opt-in link.

Common setup problems

• "Tester can't find the app": they opened the link with a different Google account, or they're in a country you didn't select.
• The opt-in link shows an error: the release isn't approved and live yet. Wait for the review to finish.
• Testers don't appear in the count: they opened the link but didn't tap Become a tester.
• Can't create a release: check the dashboard for unfinished setup tasks.

If testers still don't appear, go through testers not showing in Play Console: what to check. Once they're joining, see how to get 12 testers and keep them for 14 days.

FAQ