Everything you need to know about Google Play Closed Testing

Closed Testing is a Google Play Console track where you distribute a pre-release version of your app to a limited group of testers via an opt-in link or email list. Unlike Internal Testing (for your team), Closed Testing requires real external users. Google now requires all new personal developer accounts to complete a 14-day Closed Testing period with at least 12 real, active testers before publishing to production.

Yes. Since November 2023, Google requires all new personal developer accounts to maintain at least 12 active testers for a continuous 14-day period in the Closed Testing track before you can apply for production access. If even one tester drops out and you fall below 12, you may need to restart. This is why many developers use services like TesterBee to ensure compliance.

No. TesterBee operates fully within Google Play Developer Program Policies. All testing is conducted by real individuals using unique physical Android devices and legitimate Google accounts. We never use automated scripts, bots, emulators, or shared accounts, and we never request access to your Play Console credentials or source code.

Google expects testers to be genuinely engaged with your app. If testers install the app but never launch it, they are not contributing to a genuine testing period. If testers are not engaged, you may need to continue testing for longer before applying for production access.

Yes. In Google Play Console, your Closed Testing track release must be reviewed and approved by Google before testers can access your opt-in link. If your track status is still in Draft or pending initial app review, testers will see an "Item unavailable" page.

You can use either method. For Email List testing, upload the list of tester email addresses provided in your TesterBee dashboard to your Play Console Closed track settings. For Google Group testing, add our designated Google Group link to your track settings. Both methods allow testers to accept your invitation via your Play Console opt-in link.

Technically yes, but it is risky. Friends and family often lose interest after a few days. If your tester count drops below 12 at any point during the 14-day period, you may fail the requirement. And if multiple testers share devices or Google accounts, it does not look like a genuine testing group. Having a backup plan is strongly recommended.

Most developers are matched with testers within 6 to 24 hours after submitting their app's opt-in link. Once matched, testers install your app and remain active for the full 14-day period. We monitor engagement and handle all tester communication so you can focus on building your app.

No. Feedback, star ratings, and bug reports submitted during Closed Testing are entirely private between you, the testers, and your Play Console/TesterBee dashboard. Closed testing feedback does not affect your public Play Store rating or store listing reviews.

Yes. Google Play Closed Testing operates at the Play Console track level on Android Application Bundles (.aab) or APKs. TesterBee works seamlessly with apps built in React Native, Flutter, Expo, Unity, Native Kotlin/Java, Ionic, or any other framework.

TesterBee offers a full refund if Google rejects your production access application due to tester engagement issues. Our testers are real people with unique Google accounts and genuine Android devices — no bots, no emulators, no shared accounts. To date, over 1,700 apps have used TesterBee to successfully publish on Google Play.

When applying for production access after your 14-day test, Google requires details about how you recruited testers, what feedback you received, and how you improved your app. TesterBee provides a step-by-step guide to help you fill out the questionnaire accurately. Read our Production Access Questionnaire Guide for detailed tips.

If your app is paid or requires in-app purchases to test features, generate promo codes in Google Play Console (under Grow > Promo Codes) giving 100% off. You can provide these codes to your testers via TesterBee so they can download and test your app at no charge.

Pricing depends on the plan you choose. Visit our pricing section for current rates. Compared to the cost of delaying your launch by weeks — or paying for a second testing cycle after a rejection — TesterBee is designed to be the most affordable and reliable path to compliance.

Yes. Each app requires its own closed testing cycle with 12 testers. You can run multiple testing cycles simultaneously through TesterBee. Each campaign is managed independently with its own set of testers.

If your developer account already has at least one app published to production (not just in testing), you are likely exempt from the requirement. However, Google has stated that organization accounts may eventually be included. Check the Google Play Console under "Production access" to see if the requirement applies to your account.

Testers provide bug reports, usability feedback, star ratings, and written comments about their experience. This feedback helps you identify and fix issues before your app goes live on the Play Store. Many developers use this feedback to improve onboarding flows, catch crashes, and polish the user experience.

Yes. Google uses sophisticated detection to identify fake accounts, emulators, and shared devices. Signs that trigger rejection include: multiple testers from the same device fingerprint or IP range, testers who install but never open the app, and accounts created solely for testing purposes. This is why TesterBee only uses verified, real testers with genuine devices.

Closed Testing is invite-only — testers join via an opt-in link and the app is not publicly discoverable. It is required for production access on new accounts. Open Testing is a public beta — anyone can find and install your app on the Play Store. You can run both tracks simultaneously. Read our full comparison: Closed Testing vs Open Testing.

TesterBee provides a real-time dashboard where you can monitor tester activity, engagement levels, days remaining in the 14-day period, and feedback received. You can also use the Google Play Console to view your Closed Testing track metrics, including the number of active testers and their engagement data.

Our tester network spans multiple countries and includes popular devices from Samsung, Google Pixel, OnePlus, Xiaomi, OPPO, and more. Testers run a mix of Android versions, helping you catch compatibility issues across different screen sizes, OS versions, and manufacturer skins.

Yes. TesterBee testers test apps in any language worldwide. Testers use TesterBee's dedicated real-time on-screen translation tool, LingoLayer - Screen Translator on Google Play (watch video demo), which translates in-app screens, menus, dialogs, and text live so testers can thoroughly test localized user flows and report bugs in any language.

We do not currently offer a free trial. However, our refund guarantee means you only pay if the service works. If Google rejects your app due to tester engagement, we refund your payment in full. This ensures there is no financial risk to trying TesterBee.