“More testing required”
More testing required · additional testing · continue closed test · insufficient tester engagement
What you typically see
- After Dashboard → Apply for production, the account owner receives an email when review finishes.
- Outcome language asking you to continue running your closed test / that the app requires additional testing.
- You remain unable to use Production (and Open testing stays gated behind production access) until a later successful application.
What public docs say
From O1:
- After you apply, Google reviews the submission. Review usually takes seven days or less; longer reviews can occur. Notification goes to the account owner.
- If your app requires additional testing, you may need to continue running your closed test.
- Explicit reasons O1 lists for required continued testing:
- Fewer than 12 opted-in testers, or
- Insufficient tester engagement during the testing period.
- The application form still expects concrete answers in three sections:
- About your closed test — how hard recruiting was; whether testers used all features; whether usage matched expected production behavior (and differences); summarize feedback and how it was collected.
- About your app/game — target audience; value proposition; estimated first-year installs.
- About your production readiness — changes made from closed-test learnings; how you decided the app is ready.
- O1 also stresses: keep testers opted in continuously; provide clear instructions and a feedback channel; act on feedback; policy compliance is your job before applying; supply working credentials if auth is required.
Community keyword reports (not official): threads that surface the phrase “more testing required” when production access is denied — see SOURCES.md F2, F3. Treat those as keyword discovery only, not policy text.
What to fix
- Re-open closed testing and verify current opted-in count and the continuous 14-day window (requirements).
- If headcount slipped below 12 (opt-outs, incomplete joins), recruit replacements and wait for a fresh consecutive 14-day window where needed.
- If the gap is engagement, use O1’s own checklist: clear instructions, ask testers to exercise all features, collect feedback through a channel you can summarize, and ship fixes before re-applying.
- Rebuild questionnaire answers from a dated log (engagement notes, feedback themes, product changes) — empty or vague answers conflict with what O1 asks you to provide.
- Re-check policy compliance and reviewer access credentials before the next Apply for production.
- Re-apply only after thresholds and engagement evidence support the form answers.