Google Play closed testing guide: 12 testers, 14 days

What exactly does the rule say?

Personal Google Play developer accounts created after 13 November 2023 must run a closed test before publishing an app to production (everyone). The requirement: at least 12 testers must stay opted in for the last 14 days without a break.

• Organization (company) accounts are exempt.
• The number was originally 20; Google later lowered it to 12. Rules can change, so check the current wording in Play Console too.
• What matters is that testers stay enrolled. They don't have to open the app every day, but they must not leave the group or the testing program.

Set up closed testing in Play Console

1. Create your app in Play Console and build your app bundle (AAB).
2. Under Test → Closed testing, create a track (usually called "Alpha" by default), create a new release and upload the bundle.
3. On the Testers tab choose Google Groups and enter the group's e-mail (group-name@googlegroups.com) under "Email addresses". Put your e-mail or this site's address in "Feedback URL or email address" and Save. You can use an e-mail list of testers' Gmail addresses instead, but then you have to update the list by hand for every new tester.
4. On the Countries/regions tab, choose where the test is available. Opening the test to all countries makes finding testers much easier, and it doesn't mean you'll publish to all countries in production.
5. Send the release for review. Closed testing releases are reviewed by Google too; once approved, the test link starts working.

The test (opt-in) link looks like play.google.com/apps/testing/your.package.name. We generate it automatically from your package name.

Play Console menu names change from time to time. If you can't find a step, typing "closed testing" into its search box usually helps.

How to create a Google Group

1. Open groups.google.com with the Google account you use in Play Console and click Create group on the left.
2. 1/3 Group info: use your app's name as the group name, pick a short group e-mail (something like myapp-test; @googlegroups.com is added automatically), write a one-line description and click Next.
3. 2/3 Privacy settings: set "Who can search for group" to Anyone on the web and "Who can join group" to Anyone can join. Both are required so testers can get in without approval. "Who can view conversations" and "Who can post" can stay at group members, and "Who can view members" at group owners, so testers don't see each other's addresses.
4. 3/3 Add members: leave it empty, testers will join on their own. Click Create group.
5. Click "Go to group"; the page address looks like groups.google.com/g/group-name, and that is what you enter when opening your request. The group's e-mail is group-name@googlegroups.com; you'll add it to Play Console in the next step.

The upside of a Google Group: when a new tester arrives you don't have to touch Play Console; anyone who joins the group can join the test.

The shared group: join once, test everything

If you don't want to create your own group, use the TestSwap shared group: testswapoff@googlegroups.com. Everyone is in the same group, so a tester joins once and an owner adds a single address in Play Console.

As an owner: choose "Shared group" when opening your request; on your track's Testers tab pick Google Groups, paste this address under "Email addresses" and Save. That's all.

As a tester: join the group once with the Gmail account you use on the Play Store. After that you can opt in to any test directly. Google counts you by clicking each app's opt-in link, not by group membership, so that step stays in every test.

If you leave the group you drop out of every test that uses it at the same time, and your 14-day clock in those tests resets. Members can't see each other and the group sends no e-mail.

Find your testers here

Here, everyone is someone's tester. It works like this:

1. Reserve seats in other people's tests first. As you earn points, your own request moves up the list.
2. Add your app and choose how many testers you need. The default is 15 seats: 12 required testers and 3 spares. If you already have some testers, pick only what you are missing; the spares shrink accordingly. Even if a few people drop out, your count holds.
3. When the seats fill up, start the test. Everyone joins on the same day, so the 14 days end together.
4. Testers prove with screenshots that they joined, and that they're still in the test when the period ends.

What to watch during the 14 days

• Keep your count. If you drop below 12 testers, your period may be at risk. That's what the spare seats are for.
• Collect feedback. Testers write feedback as they try your app. It improves the app and strengthens your application to Google.
• Review proofs on time. Proofs you don't review are approved automatically after 48 hours, but quick approval keeps testers motivated.

Apply for production access

When the period ends, the option to apply for production access appears on the Play Console dashboard. Google asks a few questions: how you ran the closed test, how you recruited testers, what feedback you received and what you changed, and whether the app is ready for release.

• Be specific and honest. Say clearly that you found testers through a testing community.
• Use the feedback summary. On My apps, the "Export" button in the feedback section gives you everything as one text.
• Describe changes with examples, like "we fixed this bug, we simplified that screen".

According to guides, vague answers are the most common reason for rejection. A reply can take a few days; testers should stay in the test meanwhile.

If Google asks for more testing

Google sometimes asks for more testing. In that case, start a new round with the "Google asked for more testing" button on your app's management page. Testers are asked whether they'll continue; staying is optional and those who stay earn extra points. Seats of those who leave open up to new testers in the first hours.