Good to know·3 min read
Do you need 12 testers for every new app?
How the requirement applies to your second, third, and tenth app.
Short answer: yes. Google's closed testing requirement applies per app, not per account. Every new app you publish from a personal developer account created after November 13, 2023 runs its own closed test, 12+ testers opted in for 14 days, and submits its own production access application. Completing it once does not unlock the account for future apps.
| Repeats for every new app? | |
|---|---|
| Closed test, 12+ testers for 14 days | Yes |
| Production access application | Yes |
| $25 developer registration fee | No, paid once per account |
| Adding the testers Google group in Play Console | Yes, about two minutes per app |
| Testing updates to a live app | No, apps with production access ship updates directly |
- 1
Set up the new app's closed track
Create a closed testing release for the new app and add the same Google group you added last time. The group email never changes, and Google is fine with the same testers covering multiple apps: the requirement is one test per app, not new people each time. The setup guide shows every screen. - 2
Submit the app on Testers Community
Each app is its own submission with its own plan. Head to Submit App, add the new app's details, and our testers opt in within 6 hours, exactly like your first test. - 3
The calendar runs the same
Reports by day 10, apply for production access on day 15, and Google typically approves by day 17. The 14-day testing guide covers the full timeline.
Who skips this entirely
Organization accounts registered with a D-U-N-S number are exempt from closed testing, and so are personal accounts created before November 13, 2023. And once any app has production access, its future updates go straight to production with no new test.
Stuck on something? We are one email away.
support@testerscommunity.com