What is Google Play closed testing?
Closed testing is a mandatory step imposed by Google since November 2023 for all new developer accounts on Google Play Console. Before that date, any developer could publish an app directly to production. Now, it is necessary to go through a complete testing cycle before making the app available to the public.
In practice, closed testing works like this: the developer creates a closed testing track in Google Play Console, uploads the APK or AAB, and adds a group of testers. These testers receive a link to join the test and install the app directly from the Play Store — but the app is only visible to them, not to the general public.
Google's goal with this requirement is to ensure the quality of apps that reach the Play Store. Before, thousands of malicious, low-quality, or fraudulent apps were published daily. Closed testing forces the developer to validate the app with real people before distributing it to millions of users.
This policy specifically targets new developer accounts (personal accounts created after November 2023 and organizational accounts that haven't published yet). Developers with older accounts that already have published apps are not affected.
Google's technical requirements for closed testing
Google establishes five main requirements that need to be met simultaneously for closed testing to be considered valid:
Minimum 12 opt-in testers
Twelve real people need to accept the invitation and install the app. Their Google accounts must be legitimate — with real Play Store history (downloads, reviews, time of existence). Recently created, inactive, or history-less accounts are automatically disregarded.
14 consecutive days of testing
The testing cycle needs a minimum of 14 continuous days of real app usage. This means testers need to open and use the app regularly throughout the period. If the cycle is interrupted, the counter resets to zero.
Real, certified physical devices
The Google Play Integrity API checks each device used in testing. Emulators (Android Studio, Genymotion, BlueStacks), virtual machines, rooted devices, unlocked bootloaders, or custom ROMs are detected and rejected.
Real, organic, and consistent usage
Google analyzes app usage patterns during the cycle: session time, number of interactions, navigated flows, opening frequency. Robotic behavior is detected and flagged.
Complete production form
After the 14-day cycle, the developer needs to fill out a production form explaining: what the app does, which features were tested, which bugs were found and fixed, and why the app is ready to be published.
How to create closed testing in Google Play Console
Create your developer account
Go to play.google.com/console and create your account (personal or organizational). The cost is $25 (one-time fee). Organizational accounts need D-U-N-S verification.
Create the app in the Console
Click "Create app", fill in the name, default language, type (app/game) and content/ads declarations. Configure the store listing (description, screenshots, icon).
Configure the closed testing track
Go to Testing > Closed testing > Create new track. Upload the AAB (Android App Bundle). Configure the track name and testing regions.
Create a testers list
In the closed testing section, create an email list. Add at least 12 email addresses of real Google accounts. Google generates an invitation link for testers.
Distribute the invitation link
Share the generated link with your testers. They need to accept the invitation, making them "opt-in". Then they install the app from the Play Store normally.
Wait for the 14-day cycle
Testers need to use the app for 14 consecutive days. After the cycle, the "Request production access" button becomes available in the Console.
Fill out the production form
Answer all questions on the form: tested features, fixed bugs, reason for publication. Submit and wait for Google’s review (3-7 business days).
The 5 most common closed testing mistakes (and how to avoid them)
Using testers from Telegram groups
High RiskFree groups like "Play Store Testers" seem like the easy solution, but accounts are fake, disposable, and uncommitted. Google detects them through account history and the Play Integrity API. Result: weeks wasted with testers that Google silently discards.
Hiring bot or automation services
Critical RiskCheap services that promise "20 testers for $10" use emulators and scripts. The Play Integrity API detects 100% of these devices. Worse: Google can permanently ban your developer account for policy violations.
Asking friends and family
Medium RiskGood intentions, but doesn’t work in practice. Of the 15 people you ask, 4 install, 2 open it once, and nobody maintains commitment for 14 days. The cycle never completes because people without professional incentive don’t use the app consistently.
Ignoring the production form
High RiskEven with a perfect testing cycle, a poorly filled production form results in rejection. Vague answers like "tested everything" or "no bugs" raise red flags. Google wants details: which flows were tested, which bugs appeared, how they were fixed.
Interrupting the 14-day cycle
High RiskIf you update the app and remove the closed testing version, or if testers uninstall mid-cycle, the counter resets. Each update needs to be made on the same testing track, without removing the previous version.
How TestsApp US solves closed testing in 14 days
Our service completely eliminates the headache of closed testing. With over 200 apps approved and a 97% first-cycle success rate, the process is simple and transparent:
You contact us via WhatsApp or Telegram, share your app's closed testing link, choose your plan and make payment. The same day, our 12+ human operators are added to the test. Each operator has a verified Google account with legitimate history and uses a certified physical Android device.
During the 14-day cycle, operators test the app daily: install, navigate through flows, interact with features, test error scenarios. Each session is documented with device model, Android version, time, and tested flows. If we identify bugs, we notify you immediately so you can fix them.
After the cycle, we fill out the production form together with you — detailing everything that was tested, bugs found and fixed, and why the app is ready. The form is submitted to Google, which reviews and approves within 3 to 7 business days.
Payment confirmed. 12+ operators added to closed testing.
Installation, basic flow, and first documented sessions on various devices.
Advanced flow testing. Feedback and support for fixes if needed.
Final tests, error scenarios, edge cases, and fix validation.
Cycle complete. Production form filled out and submitted to Google.
Google approves. Your app is published and available on the Play Store.
Frequently asked questions about Google Play closed testing
Is closed testing mandatory for all developers?
No. Mandatory closed testing applies to new developer accounts (personal accounts created after November 2023 and organizational accounts that have not yet published apps). Old accounts with already published apps are not affected.
How many days does closed testing last at minimum?
Google requires a minimum of 14 consecutive days of testing with at least 12 opt-in testers. We recommend the 14-day plan as a safety margin, since any interruption resets the counter.
What happens if I update the app during closed testing?
You can update the app during the cycle without issues, as long as the update is made on the same closed testing track. Do not remove the previous version — just publish the new version on the same track. The cycle continues normally.
Does closed testing work for games?
Yes. The process is the same for apps and games. Our operators test games the same way: install, play complete sessions, test different flows (tutorial, gameplay, in-app purchases if any) throughout the cycle.
Do organizational accounts also need closed testing?
Yes, if the organizational account has not yet published any app. Organizational accounts that already have published apps can publish new apps without going through closed testing.
What is the Play Integrity API and why does it matter?
The Play Integrity API is Google’s system that verifies if the device is real (not an emulator), if the bootloader is locked, if there’s no root, and if the Google account is legitimate. Testers with devices that fail these checks are automatically discarded from the cycle.
Can I reuse testers for another app?
Yes, the same operators can participate in closed testing of multiple apps. In fact, accounts with a history of test participation are even more valued by Google. If you have more than one app, we offer special conditions.
What is the difference between closed testing, open testing, and internal testing?
Internal testing is for up to 100 people and does not count toward the production requirement. Open testing is public (anyone can participate). Closed testing is by invitation and is the only one that meets Google’s requirement for new accounts. Our service specifically addresses closed testing.
Solve closed testing today
12+ real testers. Certified physical devices. Starting at $1.24/day. Same-day start.
Over 200 apps approved with 97% first-cycle success rate.