Why Does Google Play Say More Testing Is Required?

Even after completing a closed test and applying for production access, Google Play may tell you that more testing is required.

Meeting the numeric requirement of 12 testers for 14 days does not automatically guarantee production access. The application also asks how the test was conducted, what you learned, and how the app was improved.

Main cause 1: Twelve testers did not remain opted in for 14 days

For affected personal developer accounts, at least 12 testers must remain opted in continuously for 14 days.

The period you expected may differ from the qualifying period in situations such as:

• The twelfth tester joined several days after the test started
• One or more testers left during the period
• The tester list was changed
• A tester joined with a different Google account
• A person was added to the email list but never completed opt-in

Compare the status shown in Play Console with each tester’s participation confirmation.

Main cause 2: The actual testing was too limited

When the only goal is to collect enough participants, it becomes difficult to explain meaningful testing in the production-access application.

Examples include:

• Testers were not given specific features to check
• You did not confirm whether they used the app after installation
• No feedback was collected
• No bugs or usability issues were identified
• No updated build was ever distributed

An update is not always required. However, you should be able to explain what was tested and why you believe the relevant behavior worked correctly.

Main cause 3: Feedback records are too vague

Records such as the following do not show what the test actually covered:

There were no problems.
Everything worked for everyone.

Instead, record the tested features and conditions in concrete terms.

Twelve testers checked registration, sign-in, image upload, and history storage.
Two testers said the save-completion state was difficult to understand, so we changed the button text and added a completion message.
We published the revised build to the same track and asked the testers to verify the change again.

Main cause 4: The application answers look generic

Copying sample text written for another app often produces answers that do not match your real test.

Your answers should include:

1. Who the testers were and how they were recruited
2. What they tested
3. Specific feedback received
4. Changes or improvements made
5. What was checked before requesting production access

Use How to Answer the Google Play Production-Access Application as a structure, but replace every example with facts from your own app.

Main cause 5: The test and the application do not match

Credibility is reduced when the application says a feature was thoroughly tested even though that feature was disabled in the closed-test build.

Do not claim that an untested feature was tested.

This closed test focused on the free features and account-management flows.
The purchase flow was checked separately with license testers.

What to do before reapplying

When Google Play asks for more testing, do not immediately resend the same answers. Conduct additional testing and improve the supporting records.

1. Recheck participation

• Are at least 12 testers currently participating?
• Are they using the invited Google accounts?
• Did they complete opt-in?
• Has anyone left the test?
• Can they receive the latest version?

2. Define the test scenarios

• First launch
• Registration and sign-in
• Core features
• Data saving and synchronization
• Error messages
• Screen clarity
• Behavior on multiple devices and Android versions

3. Record the feedback

4. Publish a revised build when necessary

When you make changes, increase the versionCode and publish the new build to the same closed-testing track.

5. Make the answers more specific

Clearly explain what was added after the previous application.

After the previous application, we conducted additional closed testing.
Testers reported that the sign-in failure guidance and save-completion state were unclear, so we revised the wording and screen transition.
We then asked testers to check the revised build and confirmed that the target flows completed successfully.

Actions to avoid

• Inventing tester activity that did not occur
• Claiming changes that were not implemented
• Repeatedly submitting the same answers within a short period
• Asking people only to join without using the app
• Assuming approval is guaranteed
• Saying that a third party guarantees production access

Summary

A more testing required result is not necessarily caused only by the tester count.

Check whether:

• Twelve testers remained opted in continuously for 14 days
• Testers actually used the app
• Specific feedback was recorded
• Feedback led to fixes or further verification
• The application answers match what really happened

For a step-by-step reapplication process, see How to Reapply After Google Play Requires More Testing.