PeerPlay
Free never means zero cost here. Every free route to 12 testers is paid for with your own time, and the real question is which hours actually carry you through 14 days instead of leaving you short on day 9 and waiting all over again.
So I ranked the free options by three things: whether people stay opted in for the whole 14 days, whether they actually open the app, and how many of your hours it takes to get there. Getting someone to tap an opt-in link is easy. Keeping 12 people around for two weeks is where most free plans fall apart.
Here's the order I'd try them in, best first.
1. A reciprocal exchange that tracks activity
This is my top pick, and yes, I'm biased, because PeerPlay's free Mutual Exchange tier is one of these. The model is simple. You test other developers' apps to earn credits, then spend those credits to get testers for your own app. Nobody pays money. Everybody pays in testing time.
What makes an exchange work is the tracking, not the swap. A swap with no checks turns into people installing your app once and forgetting it exists. PeerPlay checks that a tester actually opened the app for a real minimum session, not just installed it, and removes testers who go quiet during a round. That's the part that keeps your count from quietly sliding under 12.
The cost is daily attention. You'll be opening other people's apps for the length of a round, so this suits you if you can spare a few minutes every day.
2. Developers you already know
Other Android developers are the best testers you can recruit by hand. They know what opting in means, they won't uninstall your build because it looks unfinished, and they understand why you need them for 14 days in a row.
Ask people you actually know: colleagues, classmates from a course, regulars in a community you're really part of. The limit is numbers. Most of us don't know 12 Android developers, and each favour is one you'll probably repay by testing their app later. That's fair. It just means this route usually covers part of your list, not all of it.
3. Your own users and followers
If you already have a waitlist, a newsletter, users of an earlier app or a group of followers who like your work, this can be the strongest free source of all, because these people want your app to exist.
Post the opt-in link with plain instructions: Android phone only, join with the same Google account you use on the Play Store, install the app, keep it for two weeks and open it now and then. Spell out that last part. People who aren't developers assume installing is enough.
It sits third only because most first-time developers don't have an audience yet. If you do, start here.
4. One-to-one swaps with developers asking for testers
Developers post on forums and on itch.io that they need testers all the time. Replying to one of them with a direct offer, I test yours and you test mine, works much better than dropping a link into a crowded thread, because both of you know exactly who owes what. It's still how I do a lot of my own outreach, one developer at a time.
It's slow, though. Every swap is a separate conversation, and you need about a dozen of them. Keep a short list of who you swapped with, and look at your track's Testers tab every few days so you notice early if your number drops.
5 and 6. Friends, family and open test-for-test threads
Friends and family will say yes, and that's the trap. They join because you asked, then a phone gets replaced, your app gets deleted to free up space, or they just never open it again. Anyone on an iPhone can't help at all, since your testers need to install the Android build from Google Play.
Big public threads on Reddit or Discord, where everyone drops a link and promises to test back, are free and fast. They're also the least reliable option here. Plenty of people opt in, install once and move on, so you collect ghost testers who count today and are gone next week, and Play Console tells you very little about who is actually using your build.
Both are fine as extras. Use them for the last two or three spots, never as the base of your 12.
What the paid route costs instead
If your time is worth more than the money, paying is the other option. On PeerPlay, Starter Pro is $24.99 one time for 15 verified testers with no reciprocal testing, and Production Pass is $34.99 one time for 12 guaranteed testers with automatic replacements. Other services charge different amounts and prices change, so check each provider's own pricing page before you compare.
One more route skips the list entirely. Organization developer accounts are currently exempt from the 12-tester rule. That needs a real registered organization and a DUNS number, so it's no shortcut for most solo developers, but if you already run a business it's worth checking before you recruit anyone.
My honest take: combine the top two or three free routes, aim for a few more than 12, and stop spending energy on open threads once your list is solid.
FAQ
How many testers should I recruit if I need 12 for Google Play?
Recruit a few more than 12. A buffer of three to five extra testers covers people who reset a phone, delete the app or simply forget about it. If the opted-in count falls below 12, you can lose progress toward the 14 days, so the buffer is cheaper than starting over.
Do closed testers have to leave a Play Store review?
No. The closed testing requirement is about testers being opted in for 14 days, and a public review isn't part of it. Private feedback still helps, though, because the production access application asks you about your testing, and real feedback you acted on gives you something concrete to describe.
Is it against Google Play policy to swap testing with other developers?
I'm not aware of any Google Play policy that forbids developers from testing each other's apps, and reciprocal testing is common. What matters is real use: testers who opt in, install and actually open the app. Policies change, so check Play Console Help if you want to be sure.
Can I use my own second Google account as a tester?
I wouldn't rely on it. Google hasn't published exactly how it judges testers, but a handful of accounts that all belong to you is unlikely to look like real testing, and it doesn't produce any genuine feedback. Spend that effort on finding one more real person instead.