Guides to Google Play closed testing

The 12 testers for 14 days requirement, explained

Google requires 12 testers opted in for 14 continuous days before production access. What that means exactly, who it applies to, and how to satisfy it.

How to verify a tester actually opted in, in Play Console

Asking a tester if they opted in is not verification. Here is where Play Console shows the real number, and how to reconcile it against your list.

Testers opted in but your count is short: 6 causes

Your testers say they opted in and Play Console still shows fewer than 12. The six things that actually cause this, and how to tell which one you have.

Can you use your own accounts as testers on Google Play?

Filling the 12-tester requirement with accounts you control is technically possible and a bad trade. What Google looks at, and what it costs when it fails.

Free vs paid app testers: an honest comparison

Four ways to get 12 testers for Google Play closed testing, what each actually costs you, and when paying is the better decision.

What happens if a tester opts out during your 14-day test

A tester leaving mid-test can reset your 14-day closed testing clock. Here is what Google actually counts, and what to do the day it happens.

Does uploading a new build reset the 14-day testing clock?

Short answer: no. Uploading a new APK or AAB to your closed track does not restart Google Play's 14-day continuous testing requirement. Here is what does.

Closed testing vs internal testing: which one Google requires

Internal testing does not satisfy Google Play's 12-tester requirement. Here is the difference between the tracks and which one unlocks production access.

Production access denied after closed testing: what to check

You ran the 14 days with 12 testers and Google still said no. The usual reasons production access is refused, and what to do about each one.