How to get 12 testers for Google Play's closed test

Before your app can go live, it has to sit in a closed test with at least 12 testers. Each one has to stay opted in for the 14 days just before you apply. Someone who joins and leaves after a week doesn't count. If a tester leaves and comes back, their two weeks start again from zero.¹

The number used to be 20. Google cut it to 12 in December 2024, after smaller developers said 20 was hard to find. Its reason for the rule in the first place was quality. Developers who test before launch, it said, tend to ship better apps and get more installs.²

The rule is for personal accounts.¹ An organisation account is set up for a business, and Google needs a D-U-N-S number to verify one. Getting that number from Dun & Bradstreet is free, so ignore anyone charging you for it. Some apps have to use an organisation account anyway, such as financial and health apps.³

If you're one person building on weekends, you probably have a personal account. Plan for the 14 days. Don't plan around them.

In Play Console, go to Test and release, then Testing, then Closed testing. Under Testers, you can add people's email addresses as a list, or point it at a Google Group so anyone who joins the group can test. A group is easier when people come and go.⁴

Your testers need a Google account and an Android phone. The opt-in link only shows up after the test is published, and it can take a few hours to work the first time.⁴ Sort all of this out first. Sending people a link that's broken is the fastest way to lose them.

Start with the people who'd actually use the app. A budgeting app? Ask the friend who's always broke by the 20th. A school app? Your old classmates, or a lecturer who complains about the portal.

Then go wider. Family members with Android phones. Your church or mosque group, your estate WhatsApp group, the group from your last job. Ask the admin before you post. A short message works best. Say what the app does, that you need them for two weeks, and that you'll send a link.

iPhone users can't help with this one, so ask early who uses Android. And recruit 15 or 16, not 12. A few will drop out. Phones get stolen, people change SIMs, someone uninstalls everything when their storage fills up.

Search for “12 testers” and you'll find people selling them. It's tempting. But when you apply, Google asks how easy testers were to find, whether they used the app's features, and what feedback you got and how you collected it. It also asks what you changed because of it.¹

Twelve strangers who install the app and never open it give you nothing to write in those boxes. Google's own page says you may be asked to keep testing if engagement is too low, and that can cost you another two weeks or more.¹

Tell people up front that they have to stay in for two weeks. Make a WhatsApp group for the testers, so feedback lands in one place and you can remind everyone at once. Give them something specific to try each few days. “Add an expense and tell me if anything confused you” gets far more back than “let me know what you think”.

Around day seven, check in. Fix one thing someone reported and tell the group it's fixed. People stay when they can see their feedback mattered.

Testers can't leave public reviews on a test version, so give them a way to reach you.⁴ An email address or the WhatsApp group is enough. Keep notes as you go, because you'll need to sum it all up later.

When your testers have been in for 14 days, there's an Apply for production button on the Play Console dashboard. The form has three parts. Your closed test: how you found testers, what they did and what they said. Your app: who it's for and why they'd want it. And whether it's ready: what you changed after testing and how you decided it was done.¹

Answer plainly, from your notes. Google says the review usually takes seven days or less.¹

On Prow: Posting your app on Prow is free, even before it's on the store. If your test uses a Google Group, put the group's link on your project page. People browsing Prow can join the group, opt in, try the app and leave feedback on your page. It's a good place to find the last few testers, and the feedback is all in one place when you apply.

• You know whether you have a personal or an organisation account.
• The closed test is published and the opt-in link works.
• You've asked 15 or 16 real people with Android phones, not 12.
• Testers know they're in for 14 days, and there's one place for their feedback.
• You fixed something they reported and told them.
• You kept notes, so the production form is easy to fill in.