Get 12 Testers for Google Play Closed Testing

Google requires new personal developer accounts to have a closed test running with at least 12 testers opted in continuously for 14 days before applying for production access. Twelve is the minimum — more testers is always allowed, and many developers add a buffer. The important part is that those testers are genuinely using the app during the window.

Most campaigns are live within 6-12 hours. Once you submit your Play Store opt-in link, we match you with 12 real Android testers who opt in within 24 hours. The 14-day clock starts as soon as testers begin engaging with your app.

We provide 14-15 testers as a buffer so even if someone becomes inactive, you stay above the 12-tester minimum. Our team monitors engagement daily and can replace inactive testers if needed.

Every TesterBee tester is a real person with their own Android device and a legitimate Google account. Google's requirement is about genuine, engaged testers, so artificial or automated activity is the wrong approach. We provide real, verified testers because it is the only way to safely meet the requirement.

Yes. If Google rejects your production access application due to tester engagement issues, we provide a full refund. We are confident because our testers are real and engaged.

Testers use real Android devices — physical phones, not emulators or virtual machines. A mix of device models and manufacturers is good practice: it shows your app works across the Android ecosystem, which is what a production release needs. It is simply better testing, and it reflects well on your application.

Yes, consistent daily engagement is ideal. While Google does not publish exact thresholds, testers who install and never open the app, or who only open it once, may not count. Daily engagement across the full 14 days is the safest path to approval.

After 14 consecutive days with 12 or more active testers, the "Apply for production" button becomes available in your Play Console. You fill out a questionnaire where Google asks what feedback you received, what changes you made, and why your app is ready for the public. Google then reviews everything — this typically takes 2 to 7 business days. It is not automatic — you need to show evidence that genuine testing happened. We guide our users through the questionnaire with specific, reviewer-ready answers based on their testing data.

Yes. TesterBee has a Free Public Testing option in our Android app where you earn coins by testing other developers' apps, then spend those coins to get testers for your own app. It is free — no credit card, no upfront payment. The trade-off is that you need to actively participate: test other apps, earn coins, keep your balance topped up. It works well for developers with time but limited budget. Our paid Private Testing plan at $14.99 is the hands-off version — we handle everything while you focus on building your app.

Our tester network covers 120+ countries. The largest concentrations are in the United States, India, Bangladesh, Pakistan, Nigeria, Brazil, and Southeast Asia. When setting up your Closed Testing track in Play Console, you enable the specific countries where your matched testers are located — we will tell you exactly which ones based on your tester group. Having testers across different regions is a plus because it shows your app works globally.

On December 11, 2024, Google officially reduced the minimum closed testing requirement for personal developer accounts from 20 testers to 12 testers, while maintaining the mandatory 14 consecutive day duration. Google updated the threshold to make closed testing more manageable for solo developers while still enforcing real-device verification and daily telemetry.

Yes. Organization Google Play accounts with a verified D-U-N-S number are currently exempt from the 12-tester, 14-day closed testing requirement. However, organization accounts require formal corporate verification, legal entity documentation, and a Dun & Bradstreet registration, which carries its own verification timeline.

No. Hiring real testers is explicitly allowed. Google's rule is about the tester being a genuine person on a real device who opted in and stays active — it is not about how that person found your app. What does violate policy is fake engagement: emulators, bots, cloned accounts, or one person using multiple accounts. TesterBee testers are real people on their own physical devices with their own Google accounts, and we never ask for your Play Console credentials or your source code.

Internal testing is limited to up to 100 people you invite by email, has no minimum duration, and does not count toward production access. Closed testing is the track Google's policy targets: it needs at least 12 opted-in testers staying active for 14 consecutive days before the production access application unlocks. Open testing is a public beta that anyone can join. Most developers run internal testing to verify builds, then closed testing to satisfy the requirement.

You create a Closed Testing track in Play Console and share the opt-in link with us. Testers join through that official link using their own Google accounts — there are no credentials to hand over and nothing to install on your side. If you would rather upload the tester email list yourself, we can send you the addresses instead. Our setup guide walks through the Play Console screens step by step.

Very little. Your part is uploading the build and sharing the opt-in link. After that, TesterBee monitors tester engagement daily and replaces anyone who goes inactive, so you do not chase testers. We do recommend pushing at least one small update during the window — it signals active development and gives your production access answers something concrete to point at.

A flat $14.99 covers 12 verified Android testers, a 2 to 3 tester buffer above that minimum, the full 14-day monitored testing period, automated dropout replacement at no extra cost, a written report covering device and engagement data plus bug and usability feedback, draft answers for the production access questionnaire, and free retesting if Google asks for more testing. There is no subscription and no service fee added at checkout.

Card and wallet payments are handled by Stripe, including Visa, American Express, Amazon Pay, Apple Pay, and UPI. You are charged once per app — there is no recurring billing and nothing auto-renews. If you need an invoice or a purchase order for a company account, contact us before ordering and we will arrange it.

Yes, and a large share of our campaigns are exactly this. A rejection almost always means Google did not believe the engagement was genuine, or the 12-tester count slipped below the minimum at some point in the window. We restart the 14-day cycle with a fresh tester group, monitor activity daily so the count never drops, and help you rewrite the questionnaire answers around what actually changed.

Yes. Pricing is per app, so you can run as many campaigns as you need, and they can run in parallel. Each app gets its own tester group and its own 14-day window, because the requirement is tracked per app rather than per developer account. Choose the number of apps at checkout and the price scales with the count.