Skip to content
Get startedAdd your app

Production access · Testers not engaged

“Testers were not engaged”: how to fix it

You had testers, but Google wasn't convinced they really used your app. This is the reason developers report most often, and the one a second 14-day test can fix if it's run differently.

What it means

Google lists insufficient tester engagement during the testing period as one of the reasons an app may need more testing. Meeting the numbers (12 testers, 14 days) wasn't enough on its own: the test didn't show that people used the app the way your future users will.

Google doesn't publish how it measures engagement. What it does publish is what it asks you to describe: whether testers used all of your features, whether their usage matched what you expect in production, what feedback you received and what you changed because of it.

This is a request for more testing, not a ban or a policy strike. Your closed test keeps running and you can apply again once it's stronger.

Why it happens

  • Install and forget: testers opted in, installed once and never came back. On paper the test ran 14 days; in practice it lasted a day.
  • No instructions: nobody told testers what to try, so the main flows, settings and edge cases were never touched.
  • No feedback channel: testers had nowhere obvious to report problems, so there's no record of what they found.
  • No updates during the test: Google's best practices include acting on feedback through updates. A test where the build never changed suggests nothing was learned.
  • Swap groups and favours: testers from “test my app, I'll test yours” exchanges often open dozens of apps for a few seconds. That isn't the audience Google asks you to represent.
  • Thin answers: even a good test can look weak if the application doesn't describe it. See application answers.

How to fix it

  1. Keep the closed test running

    Don't delete the track or remove testers. Google may ask you to continue the closed test; testers who stay opted in keep counting.

  2. Recruit testers who match your audience

    Google recommends a diverse group that represents your intended users. Aim for more than 12 so a few quiet testers don't sink the test.

  3. Give testers a plan

    Share a short list of tasks that covers every important feature: onboarding, the core flow, settings, offline and error cases. Spread them over the 14 days so people come back.

  4. Make feedback easy and keep a record

    Offer one clear channel (a form, an email address or a group chat) and log every bug and suggestion with its date. Google asks you to summarise this feedback and how you collected it.

  5. Ship at least one update

    Fix what testers found and publish a new build to the closed track during the test. Note what changed in each version.

  6. Apply again with specifics

    After a fresh 14-day period, describe the engagement in numbers: how many testers were active, which features they used, how many bugs were reported and fixed. Our free answer helper structures this for you.

How TestBunny helps

TestBunny is built around the part Google cares about here: real use, recorded every day.

  • Real testers, daily: each tester has a personal 14-day period with daily check-ins and tasks. You see who was active on which day, and inactive testers are replaced.
  • Tasks that cover your app: scenarios run in phases (core flows, edge cases, regression after your update), so features don't go untouched.
  • Feedback on record: bug reports with steps and evidence, plus usability notes, all in one place, ready to summarise.
  • A report you can use: participation, devices, scenarios and bugs in one report. See a sample report.
  • Fast start: first testers join within 6 hours of recruiting.
  • Free re-test guarantee: if Google still rejects production access after a completed campaign, you get one free re-test per campaign. Claim it within 30 days of completion.

TestBunny can't see your Play Console and can't influence Google's review. Opt-ins on our side are reported by testers. Nobody can guarantee approval, and we don't.

Frequently asked questions

Do I have to wait another 14 days?

Developers usually report being asked for another 14 days of closed testing. Keep testers opted in and improve the test in the meantime rather than starting from zero.

Does Google track how often testers open my app?

Google doesn't publish how it measures engagement. Assume what you write in the application has to be backed by real activity, feedback and updates.

Can I reuse the same testers?

Yes, if they're real users of your kind of app and willing to test properly this time. Testers who stay opted in keep counting toward the continuous period.

Will TestBunny guarantee approval next time?

No. Google alone decides. What we offer is a well-run, documented test and, after a completed campaign, one free re-test if Google says no.

Sources

Technical details were checked against the official documentation below. Menus and defaults change between versions; when in doubt, the official page wins.

Draft your application answers

A free, private helper that walks you through Google's three sections and turns your notes into well-structured drafts. Nothing leaves your browser.

Open the free helper

See what a well-documented test looks like

Daily participation, devices, scenarios, bugs and feedback, in the same report a TestBunny campaign produces. Demo data from a fictional app.

See a sample report

Other rejection reasons

Run a closed test that holds up.

Real testers, every day on record, first testers within 6 hours of recruiting. If Google still says no after a completed campaign, you get one free re-test (claim within 30 days of completion).

Start your testSee the plans

TestBunny isn't affiliated with Google. Testers earn credits, never cash. Google alone decides on production access: nobody can guarantee approval, and we don't.