How to find 12 testers for your Google Play closed test
Google Play needs at least 12 testers opted in to your closed test, without a break, for the 14 days before you apply for production access, and the application asks how engaged they were. So you need people who will stay and actually open the app. Here are the usual ways to find them, with what each gets right and what to watch.
What a tester needs
- An Android phone or tablet with Google Play, and a Google Account. Friends with iPhones can't install your Android test build.
- To be on your tester list, or in your Google Group, with that account, and to opt in through your opt-in link.
- To stay opted in for at least 14 days. Google tells developers to make this clear to testers.
- To use the app. Google can ask you to keep testing if tester engagement was insufficient.
- If your app is paid, to buy it: closed testers pay for paid apps.
Aim for more than 12. With exactly 12, one opt-out leaves you short on the day you apply, and anyone who joins late needs 14 days of their own. How the 14 days are counted.
Friends, family and colleagues
Google's Help page puts it plainly: "The most common way to recruit testers is to use personal and professional networks."
What it gets right
- Free.
- Real people on their own phones.
- Easy to remind.
What to watch
- Many of the people you know may use iPhones.
- Interest fades after a few days, and 14 is a long time to keep asking.
- Feedback tends to be polite rather than specific.
Your future users
Google suggests finding testers where your potential users already are, such as local clubs, online groups and your social media followers, and recruiting testers who represent your app's intended audience.
What it gets right
- The most useful feedback.
- The easiest application answers, because their use of the app is close to your real users'.
What to watch
- Slow to find enough people.
- Strangers have little reason to stay for 14 days.
- Check each community's rules before you post.
Tester-swap groups
Forums, subreddits, Discord servers and apps where developers in the same position test each other's apps.
What it gets right
- Free.
- Everyone understands the requirement.
What to watch
- You test at least as many apps as you get testers from, often more.
- Swaps run on trust: when someone stops, nobody replaces them.
- Some people leave once their own app has what it needs, and a tester who opts out stops counting.
Paid tester services
Marketplace gigs and sites that sell "12 testers for 14 days".
What it gets right
- Quick to arrange.
- Little of your own time.
What to watch
- You usually can't see who the testers are, or whether each is a real person on their own phone.
- The same accounts may be testing a great many apps at once, opening yours for a few seconds a day.
- Google can ask you to keep testing for insufficient engagement, so you can pay for 14 days and still need more.
Be most careful with anything built on accounts made for the purpose, or on emulators. Google's application asks whether your testers' usage matched how real users would behave and for a summary of their feedback. Accounts that only sit opted in leave you nothing true to write, and it is your developer account that submits the answers.
Test Rounds
Test Rounds is our service, so weigh this section accordingly. A round is 14 Android developers who all test each other's apps for 14 days, so each app gets 13 testers, each with their own Google account and phone. We form the round, email everyone the testers' Google accounts and opt-in links, send a short list and a check-in every morning, and replace anyone who misses two days in a row. We never use fake or bought accounts, or emulators.
What it gets right
- 13 testers, one more than Google's 12.
- A daily list and check-in, so drop-outs show up early.
- Anyone who misses two days in a row is replaced.
- $20 per app, once, with a full refund on request until your round starts.
What to watch
- You test the other 13 apps every day for 14 days, about ten minutes a day.
- A round starts only when 14 developers have joined, so your start date depends on others.
- A replacement's own 14 days start when they opt in.
- Your testers are developers, not necessarily your target audience. Add a few real users if you can.
- Google decides production access; no service can promise it.
Side by side
| Way | Cost | Your time | Main risk |
|---|---|---|---|
| Friends, family, colleagues | Free | Asking and reminding | Too few Android users; interest fades |
| Your future users | Free | The most: finding and keeping them | Slow; strangers drift away |
| Tester-swap groups | Free | Testing others' apps, often more than you get back | Drop-outs nobody replaces |
| Paid tester services | Varies | Little | Unknown accounts and thin engagement |
| Test Rounds | $20 per app, once | About ten minutes a day for 14 days | Waiting for a round to fill |
These combine well: a swap or a round for a dependable count, plus a few real users for the feedback Google asks about. What the application asks.