Answer honestly about your real test — this checks against what Google's production-access review actually looks at, not invented metrics.
Before Google Play lets a new app go live in production, it runs an automated review of your closed testing period. That review isn't a formality — apps get rejected or delayed at this stage constantly, usually because the developer assumed a requirement was met without actually checking it against Google's own criteria. This tool walks through those exact criteria so you know where you stand before you submit, instead of finding out from a rejection email.
The check below covers the six things Google's review is known to evaluate: tester count and continuity (you need 12+ opted-in testers holding for 14 continuous days, with no dip below that count resetting the clock), whether testers actually installed through the Google Play link (sideloaded or debug installs don't count), whether they used the app's core features rather than opening it once, and whether you collected and acted on their feedback. Missing any one of these is a common reason production access gets denied even when the tester count looks fine on paper.
Why does the tester count need to hold for 14 continuous days?
Google's review looks at a continuous window, not a peak. If your opted-in count dips below 12 at any point — even for a day, even if it was 12+ every other day — the continuous-day clock resets. This is the single most common reason developers think they're ready when they aren't.
Does it matter how testers installed the app?
Yes. Testers need to install through the actual Google Play closed testing opt-in link. An APK shared directly, a debug build, or a tester who was already added but never actually opted in through Play does not count toward the requirement, even though it can look like it does from your own tracking.
What if I don't have any feedback to act on?
That's fine as long as you can show you looked. "No issues found" after a real review of tester activity is a valid answer — what Google's review is checking for is evidence of a genuine test, not a specific number of bug reports.
Is a perfect score a guarantee of approval?
No — Google alone makes the final production-access decision, and this checker only verifies the criteria it's known to evaluate. A perfect score means you've met the requirements this tool can check; it isn't a promise from Testers14 or from Google.