Short answer: recruit more than 12 testers, use a Google Group for the tester list, give testers real tasks, keep a feedback channel open, and ship at least one fix during the 14 days. Testers who opt out early do not count, and the 14 days must be continuous.
I'm Ajmal, founder of TestLancer, which runs Google Play closed testing campaigns with real people on real devices.
Who does the 12-tester rule apply to?
If your personal Google Play developer account was created after 13 November 2023, you must run a closed test with at least 12 testers who have stayed opted in continuously for the last 14 days before you can apply for production access.
Why do solo developers get stuck on this?
Friends and colleagues say yes, then never tap the opt-in link, uninstall early, or use a different Google account. If someone leaves and rejoins, their 14 days start again.
What works in practice?
- Recruit extra. Aim above 12, because some people will not opt in or will drop out.
- Use a Google Group. Add the group to your closed track in Play Console, then share the group join link first and the Play opt-in link second. Testers must use the same Google account for both.
- Check availability. Confirm country availability and device compatibility, or testers may see “app not available”.
- Give real tasks. Ask testers to sign up, complete the main flow and report anything odd — and give them a place to send feedback.
- Ship a fix during the 14 days. The production access form asks how you recruited testers, what feedback you received and what you changed, so keep notes.
Can a service run this for me?
Yes. TestLancer offers Closed Testing Packages with 12+ real testers on real devices for 14 days, alongside mobile app testing, website testing, QA testing and UX research.
FAQ
How many testers do I need?
At least 12 opted in continuously for 14 days. Recruiting more than 12 protects you against dropouts.
Can testers earn on TestLancer?
Yes. Testers and freelancers join free and are paid per test.
Where do I start?
https://testlancer.com/
Disclosure: I'm the founder of TestLancer.
Top comments (1)
Good list. One thing I'd add to point 2: tell testers to open the Google Group link and the Play opt-in link while signed in to the same Google account they use for Play on their phone. A lot of "I joined but I'm not showing up" messages I've seen came from people who joined the group on a work account and installed on a personal one. They feel opted in, but Play Console never counts them.
Two more habits that helped me keep the count stable through the full 14 days:
And on point 5, keep the update small and real. A crash fix or a confusing label someone reported is plenty, and it gives you a specific sentence for the production access form instead of a generic one.