Where to Find 12 Testers for Google Play Closed Testing

Google Play's rule for new personal developer accounts looks small on paper: at least 12 testers opted in to a closed test for 14 days in a row. In practice, finding twelve people who will opt in with the right Google account, install the app, keep it for two weeks and open it more than once is where most developers get stuck. (The rule itself is covered in the 12 testers, 14 days requirement explained.)

This guide goes through the realistic sources of testers, what each one is good and bad at, and how to keep your count above 12 once you have them.

What a useful tester looks like

Before choosing a source, be clear about what you need from each tester. It is more than a name on a list:

• A real Google account that is added to your closed track, through an email list or a Google Group.
• An Android device on which the Play Store uses that same account, so they can install the test build.
• Staying opted in for the full 14 days. Anyone who leaves early can break your continuous period.
• Actually using the app. Google asks about tester engagement and feedback when you apply for production access, and low engagement is a common reason for rejection.
• Ideally, feedback. Even a few short comments give you something to fix in an update and something concrete to write in your application.

Option 1: Friends, family and colleagues

The first place everyone looks. People who know you are more likely to help and to tell you honestly what is confusing.

• Pros: free, trustworthy, often good-quality feedback, and they are real users in the truest sense.
• Cons: many of them use iPhones, some will not understand the opt-in step, and two weeks is a long time to remember an app they do not need. Asking twelve people for a favor is also a lot of favors.

Make it easy for them: send one message with the opt-in link, a note to use the same Google account as their Play Store, and two or three specific things to try. A short reminder at the end of the first week helps a lot.

Option 2: Developer communities and tester exchanges

Because every new personal account faces the same rule, a whole ecosystem of tester swapping has appeared: subreddits, Discord servers, Telegram groups and dedicated apps where developers test each other's apps. You join someone's test, they join yours.

• Pros: free or nearly free, and the other developers understand exactly what is needed.
• Cons: it costs you time, since you usually have to test other people's apps in return. Engagement is often minimal because everyone is testing many apps at once, and people quietly uninstall once their own test is done. Feedback tends to be generic.

If you go this route, keep a spreadsheet of who joined and when, follow up with anyone whose opt-in you cannot confirm, and keep a buffer well above 12.

Option 3: Your own audience

If you already have a newsletter, a social media following, a website with visitors or users of a previous app, invite them to an early access program. A Google Group works well here: people request to join, and you never have to edit the email list on the track.

• Pros: these are your future users, so their feedback is the most relevant you can get, and they are often happy to be first.
• Cons: most first-time developers do not have an audience yet, and response rates on early access invitations are usually low, so you need to invite many more people than you need.

Option 4: Freelance marketplaces

General freelance sites have many offers to provide testers for the Play Store requirement, often at a low price.

• Pros: quick to buy, and it takes recruiting off your plate.
• Cons: quality varies widely. Some sellers only opt accounts in and never open the app, which leaves you with nothing to describe when you apply. Others reuse the same accounts across many apps or run them on emulators. There is rarely any reporting, and refunds are hard to get if the test fails.

If you buy here, ask the seller exactly how the testers use your app each day, whether they are physical devices, and what happens if testers drop out.

Option 5: A dedicated closed testing service

Dedicated services exist specifically for this requirement. They provide the testers, keep them opted in for the full period and report what happened.

• Pros: predictable, fast to start, and you can spend the two weeks improving your app instead of chasing people. Good services give you a record of daily activity and bug reports you can use in your application.
• Cons: it costs money, and the testers are not your target audience, so you should still get feedback from real prospective users when you can.

Side-by-side comparison

Red flags to avoid

Whoever provides your testers, walk away if you see any of these:

1. They ask for your Play Console login or to be added as a user on your developer account. Nobody needs that to test your app; an opt-in link and a tester list or Google Group are enough.
2. They promise guaranteed production approval. Google decides on production access and also reviews your app and your answers. An honest provider can guarantee the testing, not Google's decision.
3. They cannot say how the app is used. If testers only opt in, the counter fills up but there is no engagement behind it.
4. No plan for drop-outs. Ask what happens if a tester leaves on day nine.

How to keep testers for all 14 days

• Use a Google Group so adding a replacement takes seconds.
• Send clear instructions: the opt-in link, which account to use, and what to try.
• Give testers a reason to come back, such as a new feature or fix to look at in an update.
• Check the opted-in count on the Play Console Dashboard every few days, not only at the end.
• Thank people. Volunteers who feel their feedback mattered stay longer.

Once you have your testers, our closed testing setup guide shows how to add them to the track correctly.

Where TesterBie fits

TesterBie is a testing service in the last category. Our testers are real Android phones in a device lab, each signed in with its own Google account. You add our Google Group to your closed track and paste your opt-in link; the phones opt in, install your app from Google Play and use it every day for 14 days. Each order includes spare phones so the count stays above 12, a live dashboard and bug reports with screenshots, and we never need access to your Play Console. Plans are 13 testers for $14.99, 15 testers for $19.99 or 20 testers for $29.99 per app, paid once per app. See what is included or start a test.

Frequently asked questions