Get 12 Real Testers for Google Play Closed Testing
Real people. Real devices. 14-day guarantee. Publish your Android app to production.
Get 12 real testers in under 24 hours
TesterBee matches you with 12 real Android users who stay engaged for the full 14-day testing period. Refund if Google rejects your production access due to tester engagement.
What Is Google Play Closed Testing?
Google Play Closed Testing is a testing track in the Google Play Console where you distribute a pre-release version of your app to a limited, private group of testers. Unlike Internal Testing (which is designed for your development team), Closed Testing is meant for real external users who test your app before it goes live.
Since November 2023, Google requires all new personal developer accounts to complete a Closed Testing period with at least 12 real testers for 14 consecutive days before they can publish any app to production. This policy was introduced to improve app quality on the Play Store and reduce spam, malware, and low-quality apps.
Closed Testing is not optional for new developers. You cannot skip it, and you cannot use fake accounts or emulators. Google actively monitors tester engagement and device authenticity throughout the 14-day period. If your testers are not real, active users on unique devices, your production access application will be rejected.
Why Does Google Require 12 Testers?
Before the 12-tester requirement, anyone with $25 could create a developer account and immediately publish an app to the Play Store. This low barrier led to a flood of low-quality, scam, and malware apps. Google introduced the Closed Testing requirement to:
- Improve app quality. Every app on the Play Store should have been used by real people before it reaches the public.
- Reduce spam and malware. Fake apps and malicious software are much harder to distribute when real testing is required.
- Protect users. Users deserve apps that are functional, stable, and safe. Closed Testing ensures a baseline of quality.
- Give developers feedback. Real testers find bugs, usability issues, and crashes that automated testing misses.
Twelve testers is enough to surface most critical issues without being an unreasonable burden on small development teams. It also makes it economically impractical to flood the store with fake apps using automated accounts.
The 20 to 12 Tester Policy Change
Until late 2024, Google required 20 testers for 14 days — a significantly higher bar that frustrated many indie developers. In December 2024, Google reduced the requirement from 20 to 12 testers, making it easier for independent developers to reach production.
Before Dec 2024
20 testers
for 14 days
After Dec 2024
12 testers
for 14 days
Unchanged
Real devices
real engagement
This change applies to all new personal developer accounts. Organization and business accounts may have different requirements. Regardless of the reduced number, Google still checks that testers are real people on real devices who genuinely use the app. While 12 is the minimum, more testers means more safety margin if someone opts out mid-cycle.
How TesterBee Works
TesterBee is the simplest way to meet Google's Closed Testing requirement. Instead of spending weeks begging friends, posting on forums, or risking fake accounts, you get 12 real testers matched to your app within 24 hours.
Sign up and submit your app
Create a TesterBee account and provide your app's Google Play Closed Testing opt-in link. We review your app to ensure it is functional and ready for testing.
We match you with 12 real testers
Within 24 hours, we assign 12 real Android users to your Closed Testing track. Each tester uses a unique device and Google account — no bots, no emulators, no shared accounts.
Testers engage for 14 days
Your testers install your app, use it regularly, and provide feedback. We monitor engagement to ensure every tester remains active throughout the full 14-day period.
Apply for production access
After 14 days of active testing, you apply for production access in the Google Play Console. If Google rejects your application due to tester engagement, we refund your payment in full.
What Happens During the 14-Day Testing Period?
The 14-day testing period is not just a waiting game. Google actively monitors what happens during this time. Here is what you need to know:
Days 1-3: Onboarding
Testers opt-in via your Play Store link and install your app. Google verifies that each tester uses a unique device and account.
Days 4-7: Active Usage
Testers explore your app, use core features, and report bugs. Google tracks app opens, session duration, and feature usage.
Days 8-12: Deep Engagement
Testers use your app regularly. Inactive testers are flagged. We prompt them or replace them to keep your count at 12+.
Days 13-14: Final Review
All testers confirm engagement. You collect final feedback, fix any remaining issues, and prepare your production access application.
Step-by-Step: How to Set Up Closed Testing in Google Play Console
Setting up Closed Testing in the Google Play Console is straightforward, but missing a step can cause delays. Here is the complete process:
Upload your app bundle
In the Google Play Console, go to Testing > Closed Testing. Create a new closed track and upload your Android App Bundle (AAB). Your app must be functional — Google will reject placeholder or empty apps.
Configure tester access
Choose how testers will access your app. You can create an opt-in URL (easiest) or manage testers by email list. The opt-in URL is a link you share with testers — they click it and install your app from the Play Store.
Set country availability
Under "Manage testers," select which countries your testers can be in. If your testers are global, select all available countries. If they are in specific regions, limit access accordingly.
Complete the store listing for testing
Fill out the Closed Testing store listing — app name, short description, full description, screenshots, icon, feature graphic, and content rating. This listing is what testers see when they install your app.
Publish your closed test
Click "Publish" to make your closed test live. Google reviews the release (usually within a few hours). Once approved, your opt-in link becomes active and testers can install your app.
Share the opt-in link with testers
Send the opt-in link to your 12+ testers. Each tester clicks the link, opts in to the test, and installs your app from the Play Store. Do not sideload APKs — Google only counts Play Store installs.
For a more detailed walkthrough with screenshots, read our complete guide to publishing an Android app on Google Play.
Why Choose Real Testers?
Some developers try to cut corners — using friends and family who install the app once and never open it again, buying fake accounts, or using emulators. These shortcuts do not work. Google's automated systems and manual reviewers detect:
- Inactive testers who install your app but never open it.
- Shared IP addresses or devices used by multiple "testers."
- Emulators and virtual devices instead of real Android phones.
- Test accounts created in bulk with no real usage history.
A rejection means starting over — another 14 days with 12 new testers. Every failed attempt delays your launch by at least two weeks. Using real testers from TesterBee means you pass on the first try, saving time, money, and frustration.
Beyond compliance, real testers provide genuine value. They find bugs you missed, suggest improvements, and validate that your app works across different devices, screen sizes, and Android versions. This feedback makes your app better before it reaches the public.
What Happens If You Don't Have 12 Testers?
Without 12 opted-in testers for 14 days, your app will be rejected when you apply for production access. Google checks that testers are real people on real devices — fake testers, emulator installs, and inactive testers do not count. Each rejection means starting over with another 14-day cycle.
Common DIY Failures
Many developers try to find 12 testers on their own through Reddit, Discord, or tester exchange groups. The problem? Friends forget to install, community volunteers use emulators, and strangers opt out after a few days — resetting your 14-day clock. Each failed cycle means another two weeks of waiting.
The fastest fix is getting reliable testers who will opt in correctly, stay opted in continuously, and actually use your app. That is exactly what TesterBee provides — real testers, real devices, real engagement, with a money-back guarantee.
Want the full details? Read our guides: Closed Testing Requirement Guide · Common Rejection Reasons
TesterBee vs Other Methods: Which Is Right for You?
There are several ways to find 12 testers. Each has trade-offs in cost, speed, reliability, and risk. Here is how TesterBee compares to the alternatives:
| Method | Cost | Speed | Reliability | Risk |
|---|---|---|---|---|
| TesterBee | One-time fee | 6-24 hours | High | Minimal — refund guarantee |
| Friends and family | Free | 1-3 days | Low | Dropouts restart your 14-day clock |
| Reddit and forums | Free | 3-7 days | Medium | Hard to verify real identities |
| Social media | Free | 1-2 weeks | Low | Needs existing audience |
| Freelancers (Fiverr) | $50-$150 | 1-3 days | Medium | May use emulators or shared accounts |
| Testing exchange apps | Free (time cost) | 1-3 weeks | Low-Medium | Reciprocal testing is inconsistent |
For a detailed breakdown of every method including step-by-step instructions for free options, read our complete guide to finding 12 testers.
Pricing and Process
TesterBee offers straightforward pricing with no hidden fees. You pay once for a complete Closed Testing campaign that includes:
No recurring fees. You pay once per app. If you need testers for multiple apps, each app requires its own Closed Testing campaign.
Tips to Keep Testers Engaged for the Full 14 Days
Getting 12 testers to install your app is only half the battle. You also need them to stay active for 14 consecutive days. Google tracks app opens, session duration, and feature usage — inactive testers do not count toward your 12. Here are proven strategies to maintain engagement:
Send a welcome message
As soon as testers opt in, send a short welcome message explaining what to test, how long to spend, and how to report issues. Clear expectations lead to better engagement.
Provide a simple testing guide
Give testers a checklist of features to try, scenarios to test, and specific actions to perform. A 5-minute guided test plan is more effective than "just try the app."
Check in at key milestones
Send a quick message on days 3, 7, and 12 asking if testers have found any issues. This reminds them to open the app and shows you value their input.
Make it easy to give feedback
Include an in-app feedback button, a feedback form link, or a dedicated email. The easier it is to report issues, the more feedback you receive.
Respond to feedback promptly
When testers report bugs or suggest improvements, acknowledge them. A simple "Thanks, we will fix that" keeps testers motivated to continue providing feedback.
Push meaningful updates
If testers report issues, fix them and push an update during the testing period. This shows Google you are actively developing and responding to tester feedback.
Have a buffer — always
Recruit 14-15 testers instead of exactly 12. If one or two become inactive, you still have 12+ active testers. TesterBee includes buffer testers in every campaign.
Monitor engagement daily
Check your Play Console dashboard daily for inactive testers. If someone has not opened the app in 48+ hours, reach out or replace them immediately.
When you use TesterBee, we handle engagement monitoring for you. Our testers are pre-vetted and committed to staying active for the full 14 days. We track daily engagement and replace any tester who becomes inactive — so you never fall below 12.
Frequently Asked Questions
Do I need exactly 12 testers?
How long does the testing process take?
What if Google rejects my production access application?
Can testers uninstall the app during testing?
What kind of apps work with TesterBee?
Do I need to provide test devices?
How quickly can I get started?
Is closed testing the same as a beta test?
Get Started Today
Every day you delay your Closed Testing is another day your app is not in the Play Store. While you wait, competitors launch, users find alternatives, and your development momentum stalls.
TesterBee removes the biggest bottleneck in launching an Android app. Instead of spending weeks searching for testers, you focus on building a great app while we handle the testing requirement.
Ready to publish your app?
Get 12 real testers in under 24 hours. 14-day engagement guarantee. Full refund if Google rejects your production access.
Get 12 real testers