How to find 12 testers for Google Play closed testing
Last updated: 3 November 2026
If you have a personal developer account on Google Play, before publishing a new app you need to run a closed test: at least 12 testers opted in for 14 days in a row. Here is how the requirement works, how to set up the test and how to find testers even if you don’t know anyone.
Who has to run the closed test
The requirement applies to personal developer accounts created after 13 November 2023. Organisation accounts, such as companies, don’t have it.
Until you complete it you can only distribute the app to testers: applying for production access, that is publishing for everyone, unlocks afterwards.
The rules: 12 testers for 14 days in a row
You need at least 12 testers opted in to the closed test for at least 14 consecutive days. A tester opts in from the test’s join link and then installs the app from the Play Store.
Anyone who opts in and leaves before 14 days doesn’t count. If they leave and come back, their 14 days start over.
That’s why it’s worth starting with a few extra testers, for example 14 or 15: if someone drops out you still stay above 12.
How to set up the test in the Play Console
The steps, in order:
- Create a closed test and upload your app build (the .aab file).
- Choose how testers get access: a list of email addresses or a Google Group.
- Add the testers’ addresses: they must be the Google accounts they use for the Play Store on their phone.
- Send the test release to Google’s review and, once it’s approved, share the two links: one to join the test and one to download the app.
- Wait until at least 12 testers have opted in, then let 14 days pass in a row without dropping below that number.
- From the Play Console Dashboard apply for production access and answer the questions about the test.
What Google asks at the end
The production access application has three groups of questions: about the closed test, about the app and about how ready it is for release.
Google asks, for example, how easy it was to recruit testers, whether they tried all the features, what feedback you received and how you collected it, and what you changed after the test. So you need testers who really use the app, not just sign-ups.
The review usually takes up to 7 days, sometimes longer.
Where to find testers
Friends and family are often not enough: you need 12 people with an Android phone who stay opted in for two weeks.
On TestersSeeker you find testers among developers in the same situation as you. You don’t have to create or look for a group: add your app with its closed test link and your Google Play email, and TestersSeeker puts you in the open group. Android groups have 13 people for 14 days, so every app gets 12 testers: you try the others’ apps, they try yours.
When the group is full we also let you know by email: you have the list of addresses ready to copy into the Play Console tester list, and you can see who opted in and downloaded your app. Anyone who stalls for 48 hours on a step they could already do leaves the group, and the spot goes to the next person who signs up.
If you don’t have an app but want to try other people’s, with “I’ll be a tester” you join the open group.
Every profile shows level and completed tests, and anyone who misbehaves can be reported to the moderators.
Tips to avoid starting over
Keep a few more testers than the minimum, and ask everyone to stay opted in until the 14 days are over. A TestersSeeker Android group gives you 12 testers, which is the minimum: for some margin, also add someone you know to the tester list.
Publish updates during the test and write down the feedback you get: you’ll need it to answer Google’s questions.
Return the favour with the same care: testing other people’s apps properly is what makes swapping work.