Google Play Closed Testing FAQ

Google requires a minimum of 12 testers. You can have more, but you cannot have fewer. We recommend having 14-15 testers as a buffer — if even one drops out or becomes inactive, you fall below the minimum and risk rejection. TesterBee provides 14-15 testers per campaign to ensure you always have a buffer.

Yes, testers can uninstall the app, but this is dangerous for your production access application. If your active tester count drops below 12, Google may reject you. Always have 2-3 extra testers as a buffer against dropouts. TesterBee monitors engagement and replaces inactive testers automatically.

Google requires a minimum of 14 consecutive calendar days (weekends and holidays included). Some developers run longer tests to gather additional feedback, but 14 days is the minimum. Running longer than 14 days does not hurt — it gives you more data and shows Google you take testing seriously.

Yes, you can use the same testers for multiple apps. However, each tester must actively engage with each app they test. Simply having the same list of testers does not guarantee they will use your new app. Google reviews each app's testing data independently.

If a tester drops out or becomes inactive (no app opens for 48+ hours), replace them immediately. Your active tester count must stay at 12 or above for the full 14 days. This is why we recommend starting with 14-15 testers — you have a buffer against inactivity without restarting your clock.

The Closed Testing track in Google Play Console is free to use. The cost comes from finding and managing 12 real, engaged testers. Services like TesterBee charge a one-time fee to provide verified testers who stay active for the full 14 days. Compared to the cost of a delayed launch, this is often the most economical choice.

No, if your developer account was created after November 2023. Google requires Closed Testing before granting production access to all new personal developer accounts. Organization accounts are also expected to be included eventually. There is no way to bypass this requirement.

After 14 days with 12+ active testers, go to the Google Play Console and apply for production access. Google reviews your app, testing data, and store listing, then presents you with a questionnaire about your testing experience. What you write in this questionnaire matters — vague answers lead to rejection. See our Production Access Questionnaire template for guidance. If approved (typically within a few days), you can publish to production immediately. If rejected, fix the issues and start a new 14-day cycle.

When the policy launched in November 2023, Google required 20 testers for 14 days. After receiving extensive feedback from the developer community, Google acknowledged that finding 20 testers was unreasonably difficult — especially for indie developers, solo founders, and developers in smaller markets. In December 2024, Google reduced the minimum to 12 testers while keeping the 14-day duration the same. This was a significant win for the developer community.

No. The 12-tester closed testing requirement currently applies only to personal developer accounts created after November 13, 2023. Organization accounts verified with a D-U-N-S number are exempt. However, Google has indicated that this may change in the future as they continue to tighten Play Store quality requirements. If you have an organization account, you can still benefit from closed testing for quality assurance, but it is not mandatory for production access.

Use Google Play promotion codes. Go to your app in the Play Console, navigate to "Promotions" under the Grow section, and create a promotional code for 100% off. Generate a code that testers can redeem when downloading your app. This allows testers to install your paid app for free during the closed testing period. Make sure to set the promotion to only work in the countries where your testers are located.

Google officially warns that some services offering "guaranteed closed testing access" are scams. Red flags include: asking for your Google account password, promising instant production access without actual testing, relying on emulators or bulk accounts instead of genuine testers, and having no verifiable track record or real testimonials. Legitimate services like TesterBee provide real testers on real devices with refund guarantees, transparent pricing, and verifiable results. Never share your Google account credentials with anyone.

Internal Testing is for your development team — up to 100 testers, no review required, instant updates. Closed Testing is for external testers — 12 minimum, requires a review before publishing, and is the track Google requires for production access eligibility.

Yes. You can push updates to your Closed Testing track during the 14 days. Bug fixes and minor improvements are encouraged — they show Google you are actively responding to feedback. Major changes may require an additional review but will not reset your 14-day clock.

Google monitors app opens, session duration, and feature usage. A tester who installs the app but never opens it is considered inactive and may not count toward your 12. Testers should use your app regularly throughout the 14 days — ideally opening it on multiple different days.

Real testers have unique Google accounts with genuine usage history, unique Android devices, and varied usage patterns. If you are sourcing testers yourself, verify their Play Store profiles. TesterBee pre-verifies every tester to ensure they are real, unique individuals with their own devices and accounts.