How to find 12 testers for your Google Play closed test

Why finding testers is harder than it looks

The requirement has three parts, and the second two are where people fail. Getting 12 installs is easy; getting 12 people to remain opted in for 14 consecutive days is hard; getting them to use the app across those days — the engagement Google's reviewers look for — is harder still.

Every tester who opts out before the window ends stops counting, and if they rejoin later their days start again. That means your tester pool needs to be reliable, not just large.

Option 1: Friends, family and colleagues

The obvious first step, and still a good one for the first handful of testers. The problem is attrition: people install to be helpful and forget the app exists by day three. Nobody told them that opting out or uninstalling matters.

If you go this route, send everyone the same short message: the opt-in link, the instruction to install from Google Play with the account they opted in with, and the request to keep the app installed and open it a few times a week until a date you name.

• Works for the first 3–6 testers; rarely gets you to twelve.
• Engagement tends to be shallow unless the app is genuinely useful to them.
• Easy to brief, easy to remind.

Option 2: Developer communities and forums

Developer communities on Reddit, Discord, Telegram and similar platforms are full of people in exactly your position, which is why they work: another developer who needs testers understands the rules and will usually reciprocate. Posts that say what the app does, how long the test runs and that you will test theirs in return get far better responses than bare opt-in links.

The downsides are time and noise. Threads get buried, strangers go quiet, and you have to track who actually opted in yourself.

Option 3: Play Console Approval on TesterMandi

If what you need is to clear the requirement, TesterMandi's Play Console Approval plan does the recruiting for you. Post your app and its opt-in link in the TesterMandi Android app, choose the plan, and 12 genuine testers join your closed test directly — no reciprocal testing — and stay opted in for the 14-day window. Every tester submits a screenshot each day, so you can see participation as it happens.

The plan costs ₹1,299, billed per app, per closed test, and is purchased inside the app.

• Built around the rule you are trying to meet: 12 testers, 14 days, daily proof.
• Best for developers who need to clear closed testing and move on to production.
• Does not include detailed feedback or a testing report.

Option 4: Genuine Feedback & Testing on TesterMandi

Genuine Feedback & Testing includes everything in Play Console Approval, plus the part that improves your app: testers give meaningful feedback as they use it, bugs and usability problems are identified, and you receive a detailed testing report with issues and improvement suggestions — the material you need for the production access application. The plan costs ₹1,999, billed per app, per closed test, and is purchased inside the app.

If Google does not verify your app after the 14-day period, both plans are covered by a full refund guarantee (see the refund policy for the exact terms).

TesterMandi helps developers organize and participate in testing. Google Play production approval is determined solely by Google and cannot be guaranteed by TesterMandi.

What to tell every tester

Whichever route you take, the briefing is the same. Testers who know the rules rarely break them by accident.

1. 1Open the opt-in link and accept the invitation while signed in to the Google account you use on your phone.
2. 2Install the app from Google Play — not from a file — using that same account.
3. 3Keep it installed and stay opted in until the end date (at least 14 days). Do not opt out, even temporarily.
4. 4Open the app a few times a week and try the main features; report anything that crashes or confuses you.
5. 5Watch for update notifications and install new builds when they arrive.

Keeping testers engaged for the full window

Recruiting is half the job. The other half is giving people a reason to come back. Updates with visible changes, a short reminder on day seven, and a quick reply when someone reports a bug all keep engagement up — and engagement is what Google's review ultimately looks at.

• Recruit a couple of spare testers beyond 12 so a drop-out does not reset the timeline.
• Ship at least one update during the window and tell testers what changed.
• Ask two or three specific questions rather than "any feedback?".
• Keep a simple log of who joined when and what they reported; you will summarise it in the application.

What to avoid

A closed test exists to show Google that real people used your app. Anything that fakes that signal is a bad trade.

• Bulk-install services, bots or emulator farms — zero engagement and a policy risk to your account.
• Paying for "guaranteed production approval": nobody outside Google can guarantee it.
• Removing inactive testers from the list mid-window to swap in new ones — their days vanish with them.
• Asking testers to opt out and back in to "refresh" anything; it restarts their count.