Every way to get 12 testers for Google Play closed testing, compared

What do you need from 12 testers?

Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for the 14 days before they apply for production access (App testing requirements for new personal developer accounts; our guide to the 12 testers, 14 days rule covers it in full). The application then asks about the test itself. In Google's words, you must:

• "Select an option indicating how easy it was to recruit testers for your app."
• Describe tester engagement, including "Whether testers used all available app features" and "Whether tester usage matched expected production user behavior, including details on any observed differences".
• "Summarize the feedback received from testers and describe how feedback was collected."

And if the review finds the test lacking: "Reasons for required continued testing include having fewer than 12 opted-in testers or insufficient tester engagement during the testing period."

So each way of getting testers is judged here on four things: what it costs in money, what it costs in your time, what proof of real use it leaves you for those questions, and what can go wrong, starting with testers who leave before day 14 (see what happens to the 14 days when a tester opts out).

How do the ways to get 12 testers compare?

Prices are as listed on each service's own page on 16 October 2026; they change, so check them before you buy. The other columns are our reading of what each option or page describes, not measured data. We run TestBuddy, one of the options, so weigh that row accordingly.

Nothing in this table guarantees production access. Google reviews every application and makes the decision.

Your own network: friends, family and colleagues

This is Google's first suggestion. The testing requirements article says: "The most common way to recruit testers is to use personal and professional networks." It also asks for testers close to your users: "Recruit testers who represent your app's intended future audience."

Money. None.

Time. Finding 12 or more people with an Android phone signed in to Google Play, walking them through the opt-in, then reminding them for 14 days.

Proof of real use. What they tell you, and your app's own analytics if it has any. Google lets testers send private feedback through Google Play, which you read on the Testing feedback page in Play Console.

Risks. Most people install out of kindness, open the app once and forget it. That keeps them opted in but leaves you little to report on engagement, and a single opt-out moves your application date when you started with exactly 12.

Best when you already have users, a community or colleagues who match your audience.

Reddit and Facebook test-for-test

Some subreddits and Facebook groups exist to swap closed test invitations: you opt in to other developers' tests, they opt in to yours. Read each community's rules before you post; self-promotion rules differ from one to the next.

Money. None.

Time. Swaps happen one by one, and keeping your side of each one means opening other developers' apps for 14 days. You also have to track who opted in and when.

Proof of real use. None you can check. You cannot see whether the developer on the other side opens your app.

Risks. Strangers owe you nothing, so testers leave silently, and you usually notice only when your count drops. Any offer to swap ratings or reviews once your app is live falls under Google's ratings policy (see the risks below).

Best when you need a few more testers on top of your own network.

Free tester exchange apps

Exchange apps turn reciprocity into a system: you test other developers' apps, they test yours, and the service keeps score.

Testers Community free app

As of 16 October 2026, the Testers Community free app page describes a credit system: you "test 3 other developers' apps to earn 60 credits, and then use those credits to get 12+ testers for your own app", and posting your app puts you in "a Pack, a group of 16 developers working together for 16 days". For each app you test, it says: "Each app you test earns you 20 credits: download it, use it for a few minutes, and leave feedback."

Money. None.

Time. Testing other developers' apps to earn credits, then your part in the Pack.

Proof of real use. The page we read does not say how use is checked, or what you see about your own testers' activity.

Risks. As with any exchange, everything depends on enforcement. If a tester can earn credits without really using your app, you are back to an opted-in tester with no engagement. Ask what is measured before you rely on it.

TestBuddy

TestBuddy, which we run, groups up to 16 Android developers in a wave. Each developer tests the other apps of the wave, at least 2 minutes each a day, for 14 days. A small SDK in your closed test build measures how long each tester keeps your app in the foreground, and a tester's day counts once they reach 2 minutes. A wave starts as soon as 15 developers have a verified SDK, or on its Monday at 09:00 Paris time with 13 or more; with fewer, it waits a week. In a full wave each app gets 14 testers, who leave written feedback around day 3 and day 10, and a tester who drops is replaced.

Money. None. Joining is free.

Time. About 30 minutes a day for 14 days (15 apps at 2 minutes), installing each app once, and adding the SDK to the build in your closed test, which you remove once Google grants production access. You also need an Android phone with room for 15 apps.

Proof of real use. Minutes of foreground use per tester per day, and a production access report with sessions, minutes and the days with 12 or more active testers.

Risks. Miss a day of your own testing and your recruiting pauses until you complete the next one. You may wait for a wave to fill, and a wave that starts with 13 developers gives each app 12 testers, with no margin. The testers are Android developers, not necessarily your target audience, which Google asks you to recruit.

See how TestBuddy works for the details, or join a wave of 15 developers.

Paid tester services

These services sell testers for the 14 days. The prices below are as listed on each service's own page on 16 October 2026. Guarantees, refunds and reports are each service's commercial promise, not Google's: only Google decides on production access.

Google's testing article does not mention paid tester services, for or against. Testers Community writes on its pricing page that "Google does not restrict how you find your testers, so using a testing service is allowed." That is the service's reading. Google's article itself lists personal and professional networks, communities where your users are, and social media.

Testers Community paid plans

The Testers Community pricing page lists Starter at 14 EUR per app with 15 testers and Pro at 24 EUR per app with 25 testers and an ASO report, each paid once per app. The page shows prices in the visitor's currency: we saw euros, and its title says plans start at 15 USD. It says that "Every paid plan is served exclusively by our own team of paid professional testers", and lists a live dashboard, tester feedback reports, "pre-filled production access form answers" and a refund if production access is not approved.

Watch for: the testers are paid by the service, not drawn from your audience, and answers prepared for you still go to Google under your account, so check that they describe what really happened.

PrimeTestLab

The PrimeTestLab home page lists Starter with 12 testers at 19.99 USD (shown as 20% off 25.00 USD), Professional with 20 testers at 29.99 USD, and Enterprise with 25 testers at 27.99 USD (shown as 30% off 40.00 USD), each paid once plus a 5% service fee. The page describes a live dashboard of each tester and each day, and a bug report whose depth grows with the plan. The page says that "if Google does not approve, you choose a free retest or a full refund."

Watch for: Starter has exactly 12 testers, so a single opt-out moves your application date. The page says testers whose activity dips are replaced, but a replacement starts their own 14 days.

TestFi

The TestFi pricing page lists a closed test at 39.99 USD flat per app for 16 testers, or 64.99 USD with 5 screen recordings. It lists "Backfill if someone drops", "Written feedback from every tester" and a "Compliance report you can show Google", with the guarantee "twelve opted in on day 14, or we run it again free".

Watch for: the testers are paid by the service, not drawn from your audience. A report from the service is evidence you can describe, not a document Google asks for.

12testers.com

The 12testers.com home page lists Starter at 11.99 USD and Pro at 15.99 USD per app, or 34.99 USD for 5 apps and 64.99 USD for 10. You receive a list of tester email addresses to add to your closed track, and you confirm your order on WhatsApp. The page says "Our team will thoroughly navigate and open all pages of your app for at least 5 minutes every day" and offers video proof of the devices running your app. Pro adds remote support via AnyDesk.

Watch for: every plan has 12 testers, the exact minimum, so a single opt-out moves your date. Every plan also lists "Feedback & Rate on google play". Testers cannot leave public reviews on test versions, and Google's policy says "Don't offer rewards or incentives for ratings or reviews", so ask what that line means and decline any rating that comes with a paid plan. Adding 12 email addresses does not require anyone to control your computer remotely.

Fiverr gigs

Individual sellers on Fiverr offer testers for closed testing. Each seller sets the price and what is delivered, and gigs differ widely, so read each one closely: who the testers are, whether each one opts in through your link with their own Google account, what you will see of their use, and how many testers above 12 you get. Walk away from any gig that offers ratings, reviews or installs.

What are the risks with Google?

Engagement. Whatever the source, the application asks whether testers used all available features and whether their usage matched what you expect in production, and Google names "insufficient tester engagement during the testing period" as a reason to require more testing. Twelve testers who opt in and never open the app satisfy the count and leave the rest of the form empty.

Ratings, reviews and installs. Google Play's User Ratings, Reviews, and Installs policy sums it up: "We prohibit any manipulation of ratings, reviews, or install counts." Its key considerations include:

"Don't offer rewards or incentives for ratings or reviews."

"Don't use automated services to inflate installs or ratings."

So any option that bundles ratings, reviews or install counts with testing is a risk to your developer account, whatever it costs. Testers cannot leave public reviews for test versions anyway (Set up an open, closed, or internal test), so testing never requires one.

What Google does not say. Its testing article neither endorses nor forbids any tester service or exchange, and it publishes no engagement threshold. A service that promises approval is making a commercial promise; it cannot speak for Google's review.

Which way of getting 12 testers should you choose?

• You have users or a community close to your audience: start there. It is Google's own first suggestion, and their feedback is the most useful for the form.
• You have time but no budget: an exchange with enforced rules. Ask what it measures and what happens when a tester stops.
• You have budget but no time: a paid service. Check the margin above 12, who the testers are and what proof of use you will get, and refuse any rating.
• You can mix sources. Friends, exchange testers and paid testers can all join the same closed track through its email list or Google Group, as long as none of them is in your internal test.

Whichever you choose, aim for 15 or more testers, keep a dated record of who opted in, and collect feedback yourself, because you will summarize it for Google. Our guide on how to find testers for closed testing has more on keeping them engaged for 14 days.

TestBuddy is an independent service and is not affiliated with Google, nor with any of the services above.