TestAppsWhat is Google Play closed testing?
Closed testing is a mandatory step that Google has required since November 2023 for all new developer accounts on the Google Play Console. Before that date, any developer could publish an app straight to production. Now, you must go through a full 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 the Google Play Console, uploads the app's APK or AAB, and adds a group of testers. Those 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 the apps that reach the Play Store. Previously, thousands of malicious, low-quality, or fraudulent apps were published every day. Closed testing forces the developer to validate the app with real people before distributing it to millions of users.
This policy is aimed specifically at new developer accounts (personal accounts created after November 2023 and organizational accounts that have not yet published). Developers with older accounts that already have published apps are not affected by the requirement.
Google's technical requirements for closed testing
Google sets five main requirements that must all be met at the same time for closed testing to be considered valid:
At least 12 opt-in testers
Twelve real people must accept the invitation and install the app. The Google accounts of these testers must be legitimate — with a real Play Store history (downloads, reviews, account age). Newly created, inactive, or history-less accounts are automatically disregarded by Google's algorithm.
14 consecutive days of testing
The testing cycle must run for at least 14 continuous days of real app usage. This means testers need to open and use the app regularly throughout the entire period. If the cycle is interrupted (testers drop out, the app becomes unavailable, etc.), the counter resets to zero and the developer has to start over.
Real, certified physical devices
The Google Play Integrity API checks every device used in the tests. Emulators (Android Studio, Genymotion, BlueStacks), virtual machines, rooted devices, unlocked bootloaders, or custom ROMs are detected and rejected. Only Google-certified Android smartphones and tablets are accepted.
Real, organic, and consistent usage
Google analyzes the app's usage patterns during the cycle: session length, number of interactions, flows navigated, and how often it's opened. Robotic behavior (the same flow repeated, the same exact times, suspiciously uniform interactions) is detected and flagged. Testers need to use the app the way a real user would.
Complete production form
After the 14-day cycle, the developer must 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 for everyone. Incomplete or poorly filled-out forms are the second biggest cause of rejection.
How to set up closed testing in the Google Play Console
Setting up closed testing in the Google Play Console involves a few technical steps. Here's the complete walkthrough:
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 must go through D-U-N-S verification.
Create the app in the Console
Click "Create app," fill in the name, default language, type (app/game), and declarations about content and ads. Set up 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). Set the track name and the testing regions.
Create a list of testers
Still in the closed testing section, create an email list. Add at least 12 email addresses from real Google accounts. Google generates an invitation link for the testers.
Distribute the invitation link
Share the generated link with your testers. They need to accept the invitation, which makes them "opt-in." Then they install the app from the Play Store as usual.
Wait out the 14-day cycle
Testers need to use the app for 14 consecutive days. After the cycle, the "Apply for production access" button becomes available in the Console.
Fill out the production form
Answer every question on the form: features tested, bugs fixed, reason for publishing. Submit it 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 fix, but the accounts are fake, disposable, and non-committal. Google detects these accounts through account history and the Play Integrity API. The result: weeks lost with testers that Google silently disregards.
Hiring bot or automation services
Critical riskCheap services that promise "20 testers for $10" use emulators and scripts. Google detects 100% of those devices. Worse: it can permanently ban your developer account for violating Google Play policies. You lose the app, the account, and the $25 fee.
Asking friends and family
Medium riskThe intention is good, but it doesn't work in practice. Of the 15 people you ask, 4 install it, 2 open it once, and nobody keeps the commitment for 14 days. The cycle never completes because people without a professional incentive don't use the app consistently.
Ignoring the production form
High riskEven with a perfect testing cycle, a poorly filled-out 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 showed up, and how they were fixed.
Interrupting the 14-day cycle
High riskIf you update the app and remove the version from closed testing, or if testers uninstall the app in the middle of the cycle, the counter resets. Every update must be made in the same testing track, without removing the previous version.
How TestApps US solves closed testing in 14 days
Our service completely eliminates the headache of closed testing. With more than 800 apps tested and real testing documented on physical devices, the process is simple and transparent:
You get in touch via WhatsApp or Telegram, share your app's closed testing link, choose a plan, and pay by card. On the same day, our 12+ real human testers are added to the test. Each tester uses a certified physical Android device.
Throughout the 14 days of the cycle, the operators test the app daily: they install it, navigate the flows, interact with the features, and test error scenarios. Every session is documented with the device model, Android version, timestamp, and flows tested. If we spot bugs, we let you know right away so you can fix them.
After the cycle, we fill out the production form together with you — detailing everything that was tested, the bugs found and fixed, and why the app is ready. The form is submitted to Google, which reviews and approves it in 3 to 7 business days.
Payment confirmed. 12+ operators added to closed testing.
Installation, basic flow, and first sessions documented across various devices.
Advanced flow testing. Feedback and support for fixes if needed.
Final tests, error scenarios, edge cases, and validation of fixes.
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 every developer?
No. Mandatory closed testing applies to new developer accounts (personal accounts created after November 2023 and organizational accounts that have not yet published any apps). Older accounts with apps already published are not affected by the requirement.
What is the minimum duration of closed testing?
Google requires a minimum of 14 consecutive days of testing with at least 12 opt-in testers. That said, 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 any issues, as long as the update is made in the same closed testing track. Don't remove the previous version — just publish the new version in 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: they install them, play full sessions, and test different flows (tutorial, gameplay, in-app purchases if any) throughout the entire 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 whether a device is real (not an emulator), whether the bootloader is locked, whether there is no root, and whether the Google account is legitimate. Testers with devices that fail these checks are automatically disregarded from the cycle.
Can I reuse the testers for another app?
Yes, the same operators can take part in the closed testing of multiple apps. In fact, accounts with a history of participating in tests are valued even more highly by Google. If you have more than one app, we offer special terms.
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 join). Closed testing is invite-only and is the only one that meets Google's requirement for new accounts. Our service is specifically for closed testing.
Solve closed testing today
12+ real testers. Certified physical devices. Same-day start.
More than 800 apps tested with real, documented testing on physical devices.