Android closed testing: 12 testers, 14 days.

What Google actually requires

Personal developer accounts created after November 13, 2023 have to run a closed test before they can apply for production access. The bar was 20 testers when the rule appeared and was lowered to 12 at the end of 2024.

The 14 days only count while at least 12 testers are opted in at the same time. If someone leaves on day 9 and you drop to 11, you are no longer meeting the requirement. Organisation accounts are exempt.

When the 14 days are over, you apply for production access from the Play Console dashboard. Google asks how you recruited testers, how engaged they were and what you changed based on their feedback, so a list of names that never opened the app makes for a weak application.

Setting up the closed test

1. 1In Play Console, open Test and release → Testing → Closed testing and create a track (or use the default "Alpha" one).
2. 2Upload an app bundle to the track. It goes through review like any release, which can take a few days on a new account, so do this first.
3. 3Create a Google Group and set "Who can join" to "Anyone on the web". Under Testers in your closed track, add the group's email address as the tester list. Anyone who joins the group becomes a tester, so you never edit an email list by hand.
4. 4Copy the track's opt-in link. Each tester joins the group, opens the opt-in link with the same Google account they use on their phone, taps "Become a tester" and installs from the Play Store.
5. 5Keep the track running. Count opted-in testers, not invitations sent: people who never tap the link don't count.

Finding the 12 testers

Friends and family work until the 13th day, when someone uninstalls. The usual shortcuts, tester-swap threads and paid "12 testers" services, tend to produce people who opt in and never open the app, which is exactly what the production application asks about.

On Makers Wall, the people testing your Android app are makers with their own projects on the wall. When you tick "Google Play testing" on your project, you add your Google Group link and your opt-in link. A tester who claims your project sees both, joins the group, opts in and installs on their own, uses the app and writes a report of what broke. That report is also what you point to when Google asks what you changed.

You start with room for 3 testers per round and earn up to 8 by testing other people's projects. Testers from earlier rounds stay opted in on your track, so reopening your project for another round keeps adding to the count. Ask each tester to stay opted in until your 14 days are over.

What testers should check

• Install from the opt-in link on a real device, not an emulator.
• First launch and permission prompts: are they asked at the right moment, and does the app cope with "Deny"?
• Sign-up and sign-in, including Google sign-in on a device with several accounts.
• Back button and gesture navigation, rotation and split screen.
• Small screens, large fonts and dark mode.
• What happens offline or on a slow connection.

Questions

How many testers do I need for Google Play closed testing?

At least 12 testers opted in at the same time, for at least 14 consecutive days, if your personal developer account was created after November 13, 2023. The requirement was 20 testers until it was lowered to 12 in late 2024. Organisation accounts don't have it.

Do the 14 days restart if a tester leaves?

The 14 days only count while 12 or more testers are opted in. If you drop below 12, those days don't count toward the requirement, so recruit one or two more testers than you need.

Where can I find testers for Android closed testing for free?

On Makers Wall, makers test each other's apps: you submit yours with Google Play testing turned on and add your public Google Group and opt-in links. Testers who claim it join, opt in, install and write a report. You pay by testing other makers' projects, not with money.

Can testers join a Google Play closed test with just a link?

Not with the track alone: closed tracks only accept testers from an email list or a Google Group. Set up a Google Group anyone can join, add it as the track's tester list, and share the group link with the opt-in link. Testers then get in by themselves. Open testing has a true public link, but it doesn't count toward the 12-tester requirement.

Does Google check whether testers actually use the app?

The production access application asks how engaged your testers were and what feedback you acted on. Testers who install, use the app and report problems give you real answers to those questions.