How to set up a closed test in Play Console, step by step

In short: finish your app setup, upload a release to the closed testing track, add testers as an email list or a Google Group, and send the changes for review. Once the test is published, give testers the opt-in link and your app's Play Store URL; each of them opts in on their own.

Last checked: Source: Play Console Help and our own closed test

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs

Before you start

A closed test can start once your app setup is complete. In Google's words: “You can start a closed test after completing your app setup.” Setup means the tasks on your Dashboard: store listing, app content declarations, target audience and so on. If the Create new release button is grayed out, there's still a setup task pending on your Dashboard.

Internal testing can start before setup is complete. But the 12-tester requirement calls for a closed test, and someone who opts in to your internal test can't receive the closed test's release. The differences are in the guide to internal, closed and open testing.

Menu namesGoogle's English help pages write this path as “Test and release > Testing > Closed testing”; one page shortens it to “Testing > Closed testing”. Your screen may differ slightly; the path is the same.

Step by step

  1. Open the Closed testing page. Test and release > Testing > Closed testing. The first closed testing track is there by default; you can create another one if you need it. In our account the default track was named “Alpha”. Click Manage track next to it.
  2. Choose countries. On the Countries / regions tab, your testers' countries must be selected. Google applies the country based on where the person's Google Play account is registered, not where they physically are.
  3. Add testers. The Testers tab offers two ways. Email: you create lists; up to 200 per developer account, up to 50 per track, up to 2,000 people per list. Google Groups: you enter the group's address (yourgroupname@googlegroups.com or a Google Workspace group on your account's domain); there's no limit on the group's size. In our test the two couldn't be selected at the same time.
  4. Enter a feedback channel. A feedback URL or email address. According to Google, it appears on the tester's opt-in page.
  5. Save changes. Click Save changes at the bottom of the Testers tab.
  6. Prepare the release. On the Closed testing page, click Create new release. If it's your first release, configure Play App Signing, upload your app bundle (AAB), and enter a release name and release notes (up to 500 characters per language). If you see “Errors summary”, fix those errors first; warnings don't block publishing. Then click Save.
  7. Send for review. Saving isn't publishing. In Google's words, your changes go to the “Changes ready to send for review” section on the Publishing overview page. Click Send for review there. According to Google, processing can take “a few hours or up to seven days (or longer in exceptional cases)”. In our test, quick checks ran for a few minutes first, then Google's review followed.
  8. Share the opt-in link. Once the test's status is “Published”, copy the shareable link on the Testers tab and give it to your testers. The link doesn't appear while the status is “Draft” or “Pending publication”. After the first publication, the link can take a few hours to start working.

What does a tester do?

  • Opts in. The path Google describes is the opt-in link: “After clicking the opt-in link, testers receive an explanation of tester responsibilities and a link to opt in.” In our test, installing from the Play Store URL also opted the person in: opened with an account on the list, the Play Store page showed the app with an “Early Access” label, no separate opt-in screen appeared, and the Dashboard counted the person as opted in.
  • If you use a Google Group, joins the group first: “For closed tests using a Google Group, users must join the group before opting into your test.”
  • Installs the app from the Play Store. According to Google, while there's no open test or production release, testers can't find the app by searching Google Play; you need to share the app's Play Store URL with them.
  • Needs a Google Account to join the test.

If nobody opts in, the reasons are covered in order in this guide.

How are the 14 days counted?

Google looks back from the moment you apply: “At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days.” Tell your testers this from the start; Google recommends it too: “Inform your testers that they need to remain opted in to your closed test continuously for at least 14 days.” How leaving the test and uploading an update affect this is covered in a separate guide.

Not in the official sourcesThe tester's steps on their phone aren't described in detail beyond the opt-in link and the Play Store URL. Whether a feedback channel is required isn't stated.

Sources

All are Play Console Help pages. Anything marked “in our account” or “in our test” is what we saw in our own closed test in November 2026; Google's screens can change over time.

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs