Frequently asked questions

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.

Google monitors tester engagement — how often they open and use your app. If testers install the app but never launch it, they do not count toward the 12-tester minimum. If Google detects insufficient engagement, your production access application will be rejected, and you must start a new 14-day cycle.

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. Additionally, if multiple testers share devices, IP addresses, or Google accounts, Google may flag them as fake and reject your application.

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.

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.

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.

Pricing starts at $14.99 per app for 12 testers over 14 days. This is a one-time payment — no subscriptions. Price scales proportionally if you need more testers: $18.74 for 15 testers, $24.98 for 20 testers, $31.23 for 25 testers. All plans include priority support, free retesting, and a production access guarantee.

Yes. Each app requires its own closed testing cycle with 12 testers. You can run multiple testing cycles simultaneously. 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.

Google reviews the feedback you collected during the 14 days, the bugs discovered, and how you resolved them. They also evaluate tester engagement metrics (session frequency, duration, feature usage), tester authenticity (unique accounts, real devices, diverse IPs), and whether the 14-day minimum was met with 12+ engaged testers throughout. We provide you with detailed feedback logs and guides to help you complete this questionnaire successfully.

Yes. The 14 days are calendar days, not business days. Weekends and holidays count toward the 14-day minimum. Your testing period must be 14 consecutive calendar days — there is no way to pause the clock or skip weekends. If tester engagement drops over a weekend, it still affects your application.

Yes, you can and should push updates during the 14-day period. Bug fixes and minor improvements are expected and demonstrate active development. In fact, Google looks favorably on developers who iterate based on feedback. Just avoid major feature overhauls that could require additional review.

Closed Testing is invite-only — testers join via an opt-in link and the app is not publicly discoverable on the Play Store. It is the track Google requires 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. Open Testing does not fulfill the Closed Testing requirement. Read our Android Beta Testing guide for a full comparison of all tracks.