Google Play says “more testing required”: what to check next

First, identify the decision you received

A request for more closed testing and a named policy violation need different responses. Save the exact message, date and affected app version. If Google identifies a policy issue, follow that issue’s instructions rather than assuming another group of testers will resolve it.

Google’s guidance says eligible new personal accounts need at least 12 testers continuously opted in for 14 days before applying. It also asks about engagement, feedback and readiness, and says insufficient engagement can lead to further testing. Follow any additional period specified in your own notice. Google’s production-access guidance.

Why are my 12 testers not counting?

Start with the exact state in Play Console. An invitation or an email address on a tester list is not the same as a completed opt-in. For the affected personal-account requirement, Google checks that at least 12 people were opted in continuously during the preceding 14 days when you apply.

Use the Play Console tester setup checklist for the invitation steps. If the link itself fails, work through closed-test link troubleshooting before recruiting more people.

Find the first point where testing broke down

1. Could people join? Check the intended Google account, invitation and accessible build.
2. Could they use the main features? Resolve blocked sign-in, missing test data or paid-access issues first.
3. Did participation continue? Review opt-in continuity and follow any instructions in the notice.
4. What did you learn? Collect specific observations and record what you changed or decided to investigate.

If recruitment or dropouts are the main difficulty, compare the options in our tester-recruitment guide. If the app itself needs a closer check, consider a focused Android QA review.

Give your next testing round a clear purpose

Our recommendation is to turn the notice into a short work list. Decide what needs checking, who will check it and where the findings will be recorded.

For login-based apps, provide dedicated test accounts and dummy data. Do not give testers your Play Console password or real customer records.

Check the invitation and opt-in process

Being on a tester list is not the same as completing the opt-in flow. Google’s setup instructions explain how to share the opt-in link and how Google Groups-based tests work. Check that each tester is using the intended Google account and following the correct invitation path. Google’s testing setup instructions.

Prepare answers from your testing notes

Before applying again, make a brief record of the work completed: the journeys tried, the feedback received, the changes made and the issues still open. This gives you specific facts to work from instead of generic answers.

Useful internal headings are What we tested, What we found, What changed and What remains. These are a suggested note-taking format, not a set of answers to copy into every application.

Questions developers often ask

Will more testers guarantee approval?

A larger group can help you organise coverage, but it does not replace meaningful testing or resolve an unrelated app issue.

Do I need a fixed number of minutes or app updates?

The Google guidance linked above does not prescribe a universal daily-minute target or a mandatory number of releases. Choose tasks that fit your app, and don’t make arbitrary changes just to imitate someone else’s test.

Can a replacement tester inherit the previous tester’s days?

No. Google describes the requirement in terms of each tester’s continuous opt-in period. Plan for continuity when organising the group.

Need help keeping the test moving?

Gigsdo’s managed Google Play closed-testing support covers coordination, feedback and preparation for your next step. Start a chat with the wording of the notice and your testing stage. Leave account credentials and private customer details out.