Back to blog
Closed TestingGoogle PlayGuide

What Google checks to validate your Closed Testing (12 testers isn't enough)

Having 12 accounts in the group doesn't guarantee you pass. Here's what Google actually evaluates to approve your production access.

By TesterSplay TeamJune 4, 20262 min read

Lots of people gather 12 testers, wait 14 days, request production... and Google says no. Why? Because having 12 accounts isn't the same as 12 real testers using the app.

Here's what Google actually checks.

1. Real usage, not just installs

Google doesn't count "installs." It looks at whether the app is opened and used across the 14 days. 12 accounts that install and never open = invalid testing.

2. Continuity over the 14 days

It's not 14 random days. It's sustained use over the period. If half your testers quit on day 4, the testing loses weight.

3. Account and device diversity

If all 12 accounts come from the same device or IP, the bot-farm alarm goes off. Google wants different people on different devices.

4. Account age and reputation

Freshly created Google accounts, no history, in bulk = suspicious. Real accounts with normal phone usage carry more weight.

5. Being in the right group

Sounds obvious, but it happens: testers who "sign up" but never join the test's Google Group. If they're not in the group, they don't count, no matter how much they test.

The takeaway

The real requirement isn't "12 accounts." It's 12 real people, on real devices, genuinely using your app, 14 straight days, inside your group. That's why bots don't work and why so many people's testing "doesn't count."

Get real humans who follow through and you pass. Take shortcuts and you don't.

Share this article