A closed test is the track you must run before a new personal account can apply for production access. Setting it up takes a few minutes, but a few small mistakes stop testers from joining. This guide covers the tester side of the setup. It follows Google's help pages: testing requirements and how to set up a test. Menus change, so check them in your own Play Console.

Before you start

• Finish your app setup. Google says you can start a closed test once your app setup is complete.
• Know the requirement: at least 12 testers opted in continuously for 14 days. See the 12-tester rule explained.
• Do not add your future closed testers to the internal test. Google says a user who opts in to an internal test is no longer eligible for a closed or open test. They must first opt out of the internal test and then opt in to the closed test.

Step 1: Open your closed testing track

In Play Console go to Testing, then Closed testing, choose Manage track, and open the Testers tab.

Step 2: Choose how testers are listed

You can add testers in two ways:

Method	How it works	Good to know
Email list	You create a list of tester email addresses	A closed test can have up to 200 lists, each with up to 2,000 users, and up to 50 lists per track
Google Group	You enter the group's address, in the form yourgroupname@googlegroups.com	Only people who are members of that group can join your test

Testers need a Google Account (an @gmail.com address) or a Google Workspace account to join a test.

Which to choose? A Google Group is easier to manage: you add or remove people in the group without editing the test. An email list is simpler if you only have a few testers. Either works for the 12-tester requirement.

Step 3: Add a feedback address

Google lets you provide a feedback URL or an email address. It is shown to testers on your opt-in page. Use an address you will actually read. Google also says testers can send private feedback through Google Play, which you can read in Play Console under Ratings and reviews, then Testing feedback.

Step 4: Create and publish the release

Your closed track needs a release with a build testers can install. Google's setup page walks through this step.

After you publish a test for the first time, Google says it may take a few hours before the test link is available to testers. Later changes can also take several hours. Publish early, not on the evening you hoped to start.

Step 5: Send testers the opt-in link

Each tester opens the link on their phone, with the Google account that is on the list, and joins the test. Send them clear instructions, including that they must stay opted in for at least 14 days. Our message template for testers covers it.

Step 6: Count your testers

Write down on day 1 how many have opted in. Check again every few days. Our 14-day plan shows when.

If a tester cannot join

Read testers cannot join your closed test: what to check.

If you want help

ClosedTest coordinates real testers for the 14 days. You send us your opt-in link, and we handle the rest. See the pricing and the refund policy. Google makes the production access decision.

ClosedTest is an independent service and is not affiliated with Google.