What Google asks for
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in at the same time for at least 14 consecutive days. The bar was 20 testers when the rule appeared and dropped to 12 at the end of 2024. Organisation accounts don't have it.
Then comes the production access form: how you recruited testers, how engaged they were, what you changed because of their feedback. A list of accounts that opted in and never opened the app gives you nothing to write there.
How it works here
- 1Create a Google Group anyone can join, add it as your closed track's tester list, and copy the track's opt-in link.
- 2Post your app on the wall with "Google Play testing" ticked, and paste both links. Say in the brief that testers should stay opted in until your 14 days are over.
- 3Makers who claim your app join the group, opt in and install from the Play Store on their own device. No email lists to manage.
- 4Each one uses the app and writes a report: what broke, how bad, on which phone. Those reports are your answer to "what did you change?".
Reaching 12
Be upfront about the numbers: a new maker starts with room for 3 testers per round. Testing other people's projects and getting good ratings raises that to 7, and 1 more slot can be bought with 10 credits, so 8 per round at most.
Testers from earlier rounds stay opted in on your track, so reopening your app for a new round keeps adding to the count. Most makers combine the wall with a few people of their own (friends, an existing audience) and use the wall for the testers who actually write things down.





