Step-by-step
To get 12 testers for Google Play, set up the closed testing track, invite a retained roster, keep testers opted in for 14 days, collect feedback, and submit production access with evidence.
Before looking for testers, make sure the app can actually be installed. The package name, build, country availability, tester list, and opt-in link all need to point to the same closed testing track.
This setup check prevents the most frustrating failure: finding testers and then discovering none of them can join.
The requirement is not twelve clicks. It is twelve testers who stay opted in long enough for the 14-day period to count. That is why a retained roster is usually faster than manual recruitment.
12Tests gives you that path directly: real testers assigned after setup, retained through the campaign, and documented with a report when the window ends.
At the end of the window, review the feedback, fix critical issues, and prepare specific answers for the Play Console production access form. Google is asking what happened during testing, not just whether you found twelve people.
A written report helps you answer with confidence: who tested, what they used, what they found, and what changed before production.
Yes. You can use friends, communities, or developer groups. The risk is retention: testers must stay opted in for the full window, and replacing drop-offs can delay the submission.
Get real testers assigned and run the 14-day window with a clearer path to production access.