How to get 12 testers for Google Play

Google Play asks new personal developer accounts to run a closed test before they can publish: at least 12 testers, opted in for 14 continuous days. The steps are simple. The hard part is the people.

The steps

1. Check that the rule applies to you. It applies to personal developer accounts created after 13 November 2023. Look at your Play Console dashboard: if production access is locked, it names the closed-test requirement.
2. Make your app ready to install. Upload a signed build to a closed testing track and complete the setup Play Console asks for, such as the app content declarations. A release left as a draft is not served to anyone.
3. Create or open a closed testing track. In Play Console, open Testing, then Closed testing, and use the default track or create your own. Choose the countries where it is available. Cover every country you can; a missing one shows “not found” to testers there.
4. Add your testers. On the track’s Testers tab, add an email list or a Google Group. A group lets people join later without you editing the list. Save the track.
5. Roll out the release. Send the release and the track changes for review. Testers can only install after Google has approved it, which can take from hours to days.
6. Share the opt-in link. Play Console shows a web link for the track, in the form play.google.com/apps/testing/your.package.name. Each tester must open it signed in with the same Google account that is on your list and tap to join. Opting in is what Google counts.
7. Keep twelve opted in for fourteen days. The count that matters is testers who stay opted in together, continuously, for 14 days. Someone who opts out and back in restarts their days. Aim for more than 12 so one departure does not break the run.
8. Apply for production access. When the dashboard shows the requirement is met, apply for access. You will answer questions about your test, your app and your readiness. See the guide on those questions.

Menu names in Play Console move around. If a step above does not match your screen, follow Google’s help page, which is kept current.

Where twelve people come from

There are four realistic sources, and none is free of cost: friends and family, communities of other developers, a paid tester service, or an exchange where developers test each other. The comparison sets out the trade-offs. In every case, ask for more than twelve.

A margin is not optional

Twelve is the minimum, not a target. People forget, change phones, uninstall to free space or opt out by accident. Recruit 15 or more so that a few departures do not restart anything. TestersGuild builds this in: every app has 3 spare testers beyond the 12.

Make it easy to stay

• Send the opt-in link and say plainly that they must stay opted in for 14 days.
• Ask them to open the app now and then, and to tell you what breaks. Real use is what you will describe to Google later.
• Do not ask for public reviews. Ask for private notes, and keep them.
• Check on day 3, day 7 and day 12 that the count is still where you expect.

What the TestersGuild way looks like

Instead of recruiting yourself, you join a cohort of 16 apps. You test the other 15 apps and they test yours, for 16 days. Everyone locks a $15.00 stake of credit that is kept on finishing and lost on leaving, uses their list daily and writes a short note each week. You finish with a report. It is not open to the public yet.