Get 12 Google Play Testers for 14 Days

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. Your qualifying period begins once at least 12 testers are continuously opted in.

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 Google account. Artificial or automated activity does not produce a genuine closed test or useful feedback, so TesterBee verifies the people who join each campaign.

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.

Google's published 12-tester minimum is based on continuous opt-in, not a separate hardware rule. Android quality guidance recommends combining emulators with representative hardware. TesterBee uses physical Android devices because they reveal real performance, notifications, battery behavior, and manufacturer-specific issues.

Google does not publish a required number of daily opens or a minimum session length. The hard rule is continuous opt-in for 14 days, but Google may require continued testing when engagement is insufficient. Ask testers to use the available features, provide feedback, and stay opted in for the full period.

After at least 12 testers have stayed opted in continuously for the preceding 14 days, you can apply from the Play Console Dashboard. The form covers your closed test, your app or game, and production readiness. Google says review usually takes seven days or less, but can occasionally take longer. Completing the test makes you eligible to apply; it does not guarantee approval.

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.

TesterBee matches campaigns with testers in multiple regions. When setting up the Closed Testing track, enable the countries where your matched testers are located; the campaign instructions identify the locations you need. Geographic variety can also reveal localization, network, and device issues before release.

Google announced the reduction from 20 testers to 12 on December 11, 2024, while keeping the 14-day minimum. Google said the change gave developers more flexibility after hearing feedback about the difficulty of recruiting 20 testers.

Google's published 12-tester article applies to personal developer accounts created after November 13, 2023. Organization accounts are outside that article's scope. Check the Production section of your own Play Console dashboard instead of treating account type as a shortcut.

Google's published testing requirement does not prescribe one recruitment method. Whatever route you use, testers must join your closed test, remain opted in for the required period, and participate in a genuine test. TesterBee supplies real people on their own Android devices and never asks for your Play Console credentials or source code.

Internal testing is limited to up to 100 people you invite by email, has no minimum duration, and does not satisfy the production access testing requirement. Closed testing is the required track: at least 12 testers must remain opted in continuously for 14 days before you can apply. Open testing becomes available after production access. Many developers use internal testing to verify a build before starting the closed test.

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 participation and replaces inactive testers. Review the feedback and publish an update when the test reveals a real issue; Google asks what you changed based on what you learned.

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. Start with the reason Google provided: it may call for more testing, a stronger tester count, better engagement, clearer application answers, an app-quality fix, or a policy correction. TesterBee can run a managed test when more testing is required and help you organize answers around the feedback and changes that actually occurred.

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.