Guide 2 of 7 · Updated October 2026
How to get 12 testers for your closed test — every free way, and the paid shortcut
Short answer: The free ways that work are people you know (asked with one specific task), tester-swap communities on Reddit, Discord and Telegram, a Google Group as your tester list so strangers can join with a single link, your own audience, and tester-exchange apps. Expect days rather than hours, and recruit more than 12, because swap testers often leave as soon as their own 14 days are done. The paid shortcut is a service whose testers install, stay the full 14 days and send proof — that is what PlayTesters sells for $39.
Google Play wants 12 testers opted in to your closed test for 14 continuous days before it lets a new personal account publish. Finding 12 people is the part that stalls most solo developers. Here is every way that actually works, what each one costs you in time, and how to keep the people you find from dropping out on day 9.
Before you ask anyone: four things to have ready
- A rolled-out closed-testing release. "Saved" is not "rolled out". The first release on a closed track also goes through app review, which can take a few days — until it is live, your opt-in page says the app is not available and every tester you send there bounces. How to find and check the opt-in link.
- Countries. The closed track has its own list of countries. If a tester's Play account is in a country you did not add, they cannot join. Add every country your testers might be in (or all of them).
- A two-line brief. What the app does, what to try first, where to send feedback. People test what you point at.
- A feedback channel. A Google Form with three questions, or just "reply to this message". You will need real feedback for the production access application, so collect it from day one.
1. People you know
The fastest 12 are usually family, friends, colleagues and classmates with Android phones. The trick is to ask for exactly what you need, in one message, with the link:
Hi! I'm publishing my first app on Google Play and Google needs 12 testers before it lets me. Could you be one? Two minutes:
1. Open this link on your Android phone, signed in with your Google account: https://play.google.com/apps/testing/com.example.app
2. Tap "Become a tester", then "Download it on Google Play" and install it.
3. Keep it installed for 14 days (you can use it as much or as little as you like — opening it once or twice helps a lot).
Don't leave the test before the 14 days are over, or Google resets my counter. Thank you!
Send it one-to-one rather than to a group — people respond to a personal ask. Keep a list of who said yes and who actually joined; Play Console shows you the count but not the names.
2. Tester-swap communities (Reddit, Discord, Telegram)
Thousands of developers are in the same position, and they trade: you join my closed test, I join yours. Where to look:
- Reddit. There are subreddits created specifically for this — search Reddit for "closed testing" and "testers" and you will find communities whose entire feed is opt-in links (r/AndroidClosedTesting is the best-known one). Read the pinned rules: most want you to join a few other tests before posting your own, and to post your Google Group or opt-in link in a set format. Do not post tester requests in r/androiddev — it is against that subreddit's rules and gets removed.
- Discord. Several Android, Flutter and React Native servers have a channel for closed-testing swaps, and there are servers dedicated to it. Search Discord's server discovery for "closed testing" or "Play testers".
- Telegram. Groups named along the lines of "Google Play closed testing" or "Play Console testers" have thousands of members. Same etiquette: test first, post second, and keep your message to the link and a one-line description.
What swap testers are like: they join fast, because they want you to join back, and many leave the moment their own 14 days are done. That is the main risk — if several opt out of your test before your 14 days are up, you lose the time. Recruit more than 12 from swaps, and never rely on them alone for the last few days.
3. A Google Group as your tester list
Closed testing lets you add testers either as a list of email addresses or as a Google Group. The Group route is better for strangers: you share one link, they join the group (set it so anyone can join, or join by link), and every member is automatically on your tester list. You never have to type anyone's address into Play Console. Steps:
- Create a group at groups.google.com. Under "Who can join", choose "Anyone on the web can ask to join" or "Anyone on the web can join".
- In Play Console, open the closed track → Testers → add the group's email address (it ends in @googlegroups.com).
- Share the group link together with the opt-in link. A tester joins the group, then opens the opt-in link signed in with the same Google account, then taps "Become a tester".
Tester-swap communities often require a Google Group link in posts for exactly this reason.
4. Your own audience and the indie communities
If the app has any audience at all — a mailing list, a landing page with sign-ups, a subreddit for your niche, an X or LinkedIn following, a YouTube channel — that audience makes the best testers, because they want the app and they give real feedback. Post the opt-in link with a short "help me launch" note. Indie Hackers, Product Hunt's discussion boards and niche forums also have "looking for beta testers" threads; be specific about who the app is for and what you want tested, and reply to everyone who joins.
The upside here is the feedback: "a user asked for X, we added it in build 1.0.3" is the kind of sentence Google wants to read in your application.
5. Tester-exchange apps and sites
There are apps and websites where you earn points by testing other developers' apps and spend them to get testers for yours. They work, with the same caveats as community swaps (people leave when their own obligation ends) plus one more: you are installing a lot of unknown apps on your phone. Use a spare device if you go this route, and read each app's privacy policy like a user would.
Making testers stay the full 14 days
- Say "14 days" in the ask. People who know the deal keep it. People who think it is a one-off install uninstall after a day.
- Recruit 14–15, not 12. One dropout with exactly 12 means the replacement starts a fresh 14 days. The calculator shows what a dropout costs you in dates.
- Check the count daily. The dashboard card updates once a day or so; if it dips, replace immediately.
- Send one update mid-test. A new build with release notes ("fixed the crash two of you hit on the login screen") keeps testers engaged and gives you material for the application.
- Thank them on day 14. And ask them to stay opted in until Google has approved — you may need a second 14 days if the application is turned down.
The paid shortcut, honestly
If you do not have 12 people and do not want to spend a week in swap groups, you can buy testers. The market ranges from a few dollars to over a hundred. Whoever you pay, check four things:
- Real devices, real Google accounts. Emulator farms and freshly made accounts are what Google's review is designed to catch, and they give you nothing to write about.
- They stay 14 days. Ask what happens if a tester opts out before the end.
- Proof. Opt-in and install screenshots per tester, so you can verify instead of trusting the count.
- Feedback. A few sentences from real testers is what makes the "what did you learn" questions easy to answer.
That is the service on this site: $39 one-time, 12 real testers who join within 24 hours of receiving your opt-in link, stay the full 14 days, send proof screenshots and three written feedback notes, with a full refund if they have not joined within 24 hours. It is a paid shortcut for the recruiting step only — what you do with the test, and what you write in the application, is still yours. If you have a free way that works for you, use it.