Production access rejected: what does “more testing required” mean?

In short: while reviewing your application, Google may decide your app needs more testing; you may then need to keep running your closed test. Among the reasons Google lists are two: having fewer than 12 opted-in testers, or testers not engaging enough.

Last checked: Source: Play Console Help

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs

What does Google say?

“If your app requires additional testing, you may need to continue running your closed test. Reasons for required continued testing include having fewer than 12 opted-in testers or insufficient tester engagement during the testing period.”

Play Console Help, testing requirements page

“More testing required” in the title isn't Google's wording but the common way to describe this situation; Google's page doesn't call it a rejection, it talks about continued testing. Once the review is done, the result goes to the account owner by email. According to Google, review usually takes seven days or less, and occasionally longer.

Reason 1: fewer than 12 opted-in testers

When you apply, at least 12 people must each have been opted in continuously for the last 14 days. Google spells out two cases: a tester who leaves before 14 days doesn't count, and someone who leaves and opts back in needs 14 consecutive days. Check this number before you apply. Details are in the guide to updates and the 14 days; opt-in problems are covered in this guide.

Reason 2: insufficient engagement

Google doesn't say how “insufficient tester engagement” is judged: there's no measure such as daily opens, time spent or number of feedback items. What it does describe is what the application form asks and what Google recommends:

  • The form asks whether testers used all of the app's features and whether their usage matched your expectations.
  • Google recommends giving testers clear instructions, specifying the type of feedback you want to collect, and encouraging them to “use as many features as possible”.
  • It recommends a clear feedback channel: email, a website or a messaging forum. Testers can also send private feedback through Google Play.
  • It recommends responding to feedback, fixing the bugs found and publishing updates in closed testing.

Policy and quality

Google's warning: “review is not a troubleshooting step.” Submitting an app that doesn't comply with policy “leads to rejections, review delays, and lengthier appeal processes.” Four areas to check before you apply: app content and features, target audience and content rating, functional reliability (crashes, broken functionality, missing screens), and, if your app has a login, working test credentials.

What to do now

  1. Read the email carefully. Note which reason it gives.
  2. Don't stop the closed test. Keep testers opted in; don't pause the track.
  3. Check the opted-in count. At least 12 people must have completed their 14 days.
  4. Actually increase engagement. Give instructions, announce the feedback channel, record the feedback that comes in, fix bugs and publish an update in closed testing.
  5. Apply again when you're ready. Part 3 of the application form asks what you changed based on what you learned in the closed test; say clearly what changed. The questions are in the application form guide.
Not in the official sourcesWhether the 14 days start over when you reapply. Whether you have to wait before reapplying. How many times you can apply. How engagement is judged to be sufficient. What happens if the opted-in count drops below 12 after you apply, while the review is running. Whether you reapply with the same form. The exact text of the email, and which Play Console screen shows the result. How to appeal.

Sources

Play Console Help page. Quotes are taken verbatim from the English page.

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs