"More Testing Required": What to Fix

This page is the diagnostic: what to audit in your own test evidence before you reapply. If what you need first is what the outcome means for your order — whether to reapply, retest, or claim the money-back guarantee — start with our production access rejected page instead.

If Google Play returns "more testing required" instead of production access, Google has reviewed your application and found something insufficient. Reaching the form means you cleared the initial eligibility check — it does not mean the tester requirement is behind you, since Google names a shortfall of opted-in testers among its own reasons for requiring more testing.

Google does not disclose the specific reason behind an individual "more testing required" decision. Its documentation does name two explicitly: fewer than 12 opted-in testers, and insufficient tester engagement during the testing period. The areas below are practical things to review — not a diagnosis of your particular case, and not ranked by frequency, which nobody outside Google is in a position to know:

1. Tester count on paper vs. tester count in practice. 12 opted-in testers is what Google's system checks automatically, but a reviewer can still see a roster that opted in and barely opened the app again. If your testers installed once and went quiet, the count passed but the evidence behind it is thin.
2. Engagement, not just installs. Google's questionnaire asks what testers actually did in the app — the sign-in flow, core screens, a purchase flow if you have one. "They opened it" is not the same as "they used the core features." If you can't describe specific screens or flows testers exercised, that's usually the gap.
3. Feedback that reads as invented or absent. Claiming testers found issues you can't describe specifically reads worse than saying plainly that no critical issues were found — a clean test is a legitimate answer, a vague one is not.
4. No changes made during the test. If real feedback came in and nothing in the app changed in response, the "what did you act on" answer has nothing concrete to point to. A fix pushed mid-cycle, even a small one, gives that answer something real to reference.
5. Generic answers that could describe any app. Reviewers see a high volume of these submissions; a template-sounding answer that doesn't name your app's actual screens or actual testers' devices/countries reads as low-effort regardless of whether the underlying test was fine.
6. An app or policy issue unrelated to testing at all. Occasionally "more testing required" is a proxy for a different concern — check that your app's own Play Store listing and permissions comply with Developer Policy independent of anything to do with the test itself.

The fix is rarely "wait 14 more days and hope." It's specific: real testers who actively used core features throughout the testing period, a written record of what they found, and concrete changes you made in response — see our production access questions page for what to have ready before you reapply.

What to review in your test evidence before applying again

Google doesn't publish the specific reason behind any individual "more testing required" verdict, so treat the causes above as the usual suspects, not a confirmed diagnosis of your case. What you can do concretely is audit your own test evidence against what a complete test actually produces, using the same categories a real closed-test report tracks — before you spend another 14-day cycle on a second attempt with the same gaps.

Go through each row below against what you can actually document from your own test. A gap in any row is a plausible reason your evidence read as thin, even if the exact cause Google saw was never disclosed to you.

Under our money-back guarantee, if this happens after a Testers14 order, you get a free retest or a full refund — not a second full-price order.