Android Closed Testing: How to Get 12 Testers for 14 Days

What is Android closed testing?

Closed testing is a Google Play Console testing track that lets you release your app to a limited group of people you invite. Testers install the app from the Play Store like any other app, but only people on your tester list can see it. It sits between internal testing (up to 100 people, near-instant) and open testing (anyone can join).

Who has to do it?

The requirement applies to personal developer accounts created after November 13, 2023. Organization accounts are not subject to it. Google introduced the rule to improve app quality and reduce spam apps from brand-new accounts.

The requirements

• At least 12 testers opted in to your closed test.
• They must stay opted in for at least 14 continuous days.
• Testers need a Google account and must accept your opt-in link.
• After the 14 days, you apply for production access from the Play Console dashboard.

Google has changed these numbers before (it was originally 20 testers), so always confirm the current rule in the Play Console Help Center.

How to set up a closed test, step by step

1. In Play Console, open your app and go to Test and release → Testing → Closed testing.
2. Create a track (or use the default “Alpha” track) and choose the countries where testers are located.
3. Add testers with an email list or a Google Group. A Google Group is easier because anyone who joins the group is automatically a tester.
4. Upload a signed release (AAB), add release notes, and roll it out to the closed track.
5. Wait for the review. Once approved, copy the opt-in link and send it to your testers.
6. Each tester opens the link, taps Become a tester, then installs the app from Google Play.
7. Check the dashboard: it shows how many testers are opted in and how many days are left.

Where to find 12 testers

• Friends, family, and co-workers with Android phones are the most reliable testers.
• Test-exchange communities where developers test each other’s apps. See the recommended sites below.
• Your existing audience: a newsletter, social page, or waitlist.
• Invite more than 12 (15–20 is safer) in case some opt out or uninstall.

Tips to pass on the first try

• Ship updates during the test. Google looks for real engagement, not just installs.
• Ask testers to open the app a few times and send feedback.
• Keep notes on what you fixed from tester feedback; the production application asks about it.
• Don’t remove testers or end the track before you apply.

Applying for production access

When the dashboard shows the requirement is met, click Apply for production. You’ll answer questions about your closed test (how you recruited testers, what feedback you got), your app, and whether it’s ready for release. Review usually takes a few days. If you’re rejected, Google typically asks you to run a longer test with more engagement before reapplying.

Frequently asked questions

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

New personal developer accounts need at least 12 testers opted in to a closed test for at least 14 continuous days before applying for production access.

Do organization accounts need closed testing?

No. The 12 testers / 14 days requirement applies to personal developer accounts created after November 13, 2023.

Do testers have to use the app every day?

Testers must stay opted in for 14 days. Google also looks at engagement, so ask testers to open the app regularly and send feedback.

Can I use internal testing instead?

No. Only the closed testing track counts toward the production access requirement.

What happens if a tester leaves early?

If you drop below 12 opted-in testers, the count can fall short. Invite 15 to 20 testers so you have a buffer.