How to get 12 testers for Google Play closed testing

You need at least 12 people opted in to your closed test, without a break, for 14 days, on the day you apply for production access (Play Console Help). There are five realistic ways to find them. This page compares all of them honestly, including the one we run.

What a tester actually has to do

Before you pick a source, know what you're asking people to do:

1. Use a Google account (a Google Workspace account works too).
2. Join your Google Group, if you manage testers that way.
3. Open your opt-in link and opt in.
4. Install the app from Google Play.
5. Stay opted in for 14 consecutive days.

Each step loses some people. The details, from the tester's side, are in how testers join a closed test.

How many testers to recruit

Google's minimum is 12. Aim for 15 to 20.

A tester who opts out on day 9 doesn't count, and if they come back, their 14 days start over (Play Console Help). You need 12 unbroken streaks on application day. The margin protects your calendar. The counting rules are in how the 14 days are counted.

Paid services build in the same margin: Testers Community sends 15 or 25 testers, Peerbeta 20 or 25. PrimeTestLab offers 12 or 25.

Option 1: Friends, family and colleagues

This is Google's first suggestion: reach out to friends, family, colleagues or classmates (Play Console Help).

Good: free, trusted, easy to remind in person. Weak spots: they need an Android phone. Fourteen days is long, and people forget or uninstall. Feedback is often polite and thin.

Make it work: send one short message with the link, the steps and the date they can stop. Check in on days 3, 7 and 12. Give each person one thing to try in the app.

Option 2: Your future users

Google also suggests recruiting where your users already are: an online group, a local club, your social media followers. It recommends testers who look like your target audience (Play Console Help).

Good: the most useful feedback. It also helps with the application form, which asks whether tester usage matched how you expect real users to behave. Weak spots: slow if you don't have an audience yet.

Option 3: Test-for-test groups

Developers in the same situation swap: you test their app, they test yours. These swaps happen on Reddit (for example r/AndroidClosedTesting and r/TestersCommunity), Telegram, Discord and WhatsApp.

Good: free, and you can find people within hours. Weak spots: nobody is accountable. People join, then quietly opt out a few days later. You also spend time testing other apps, and you can't easily see who is still opted in. What works and what doesn't is in free testing groups compared.

Option 4: Structured free exchanges

These are test-for-test swaps with rules, credits and tracking. They cost time, not money. Facts below were checked on each site on November 8, 2026.

• Testers Community app. You earn credit points by testing apps in "Quick Apps", then join a "Pack" of 16 developers that runs a 16-day cycle. Everyone opens the other 15 apps daily. Missing too many daily tasks earns strikes, and three strikes remove you. The free route has no guarantee (source).
• get12testers. Testing an app through its 14 days earns 20 credits. Listing your own app costs 60, so you test three apps first. Your listing has 20 slots, and the 14 days start once 17 testers have installed the app and sent first impressions. Feedback comes at five checkpoints (source).
• Peerbeta circles. 16 developers each test the other 15 apps for 14 days and get 15 testers back. Expect about 20 to 30 minutes a day. If a circle takes more than 48 hours to fill, community testers take the empty seats. Drop out and you can't join a circle for 60 days.

Good: accountability, and testers who are developers themselves. Weak spots: the daily time. Testing 15 apps a day for two weeks is real work.

Option 5: Paid services

Prices and promises as shown on each provider's own site on November 8, 2026:

Peerbeta's paid plans open as tester capacity allows. The order page shows the current start estimate.

The Fiverr numbers come from the first page of results for "12 testers 14 days": 50 gigs. Many titles still offer "12 testers or 20 testers", a sign of listings written before December 2024. What to check before ordering there is in 12 testers on Fiverr.

What to check before you pay anyone

• How testers join. Usually you add the service's Google Group or email list on your closed track. You never need to share your Play Console password.
• Proof of activity. Do you see who is opted in and active each day, or only a final message?
• What you get back. Bug reports, feature feedback, a summary you can use in the production access form?
• What happens when testers leave. Are they replaced, and does that reset anything?
• The exact guarantee. Read the conditions: when you must apply, what kind of refusal is covered, what proof you need.

What no option can do

No person or service can promise production access. Google looks at your application and decides. When it wants more testing, it names two reasons: "fewer than 12 opted-in testers or insufficient tester engagement during the testing period" (Play Console Help).

Any source can fix the first reason. The second one depends on testers who actually use the app, and on you collecting their feedback and shipping changes.

How to choose

• No budget, some time: a structured free exchange. It beats ad hoc swaps because people are held to the 14 days.
• You have an audience: recruit your future users. Add a margin from friends.
• You have a deadline: a paid service. Compare the start time, the number of testers, and what you get back at the end.
• Mix sources. Ten friends plus a structured source gives you a margin without relying on one group.

Whatever you choose, give testers something specific to do, collect what they tell you, and ship at least one update from it. That's what the application form asks about. The full process is in the complete guide to Google Play closed testing.