A developer with her head in her hands in front of a laptop.

Photo by Resume Genius on Unsplash

← All articles

BTesting

12 testers, 14 days, and still rejected. Here's why.

You ran the closed test, kept 12 testers opted in for 14 days, applied for production access, and got a refusal. It's a common story, and it usually comes down to one thing: from Google's side, your test didn't look like a test. Here is what tends to go wrong and how to run the next one.

By Maxime Bertonnier · Published

The count is the minimum, not the requirement

The 12 testers and 14 days unlock the right to apply. The application itself asks about your testing: how you recruited testers, how engaged they were, what feedback you got and what you changed. The decision is based on those answers, so meeting the count with testers who never opened the app leaves you with nothing to say.

What usually causes a refusal

  • Testers opted in but barely used the app: few sessions, no feedback through Play or anywhere else.
  • No new builds during the test, which suggests nothing was learned or fixed.
  • Vague answers on the application form ("friends and family tested it, it works").
  • The count dipped below 12 at some point, so the 14 days were never continuous.
  • The app itself isn't ready: crashes, placeholder content, policy problems.

Running a test that passes

  1. 1Read the refusal email carefully: it says what Google expects before you apply again.
  2. 2Recruit testers who will use the app and tell you what broke, not just opt in. Give them a short brief: what to try, what to report.
  3. 3Ship at least one new build during the test, fixing what testers found, and keep notes on what you changed and why.
  4. 4Keep a margin above 12 testers, so one person leaving doesn't break the run.
  5. 5Write the application from your notes: who tested, how you found them, what they reported, what you changed.

Where Makers Wall fits

I built Makers Wall for feedback, not for the count, but the two meet here. Makers who claim your Android project join your Google Group, opt in, install and write a report with every problem they found. Those reports are the substance of your application. You start with 3 testers per round and can reach 8, and earlier testers stay opted in, so combine the wall with a few people of your own if you need 12 quickly.

What not to do after a refusal

  • Don't buy a batch of testers: paid opt-ins are exactly the pattern the application is designed to filter out.
  • Don't reapply the same day with the same answers.
  • Don't create a new developer account to start over: Google's policies on related accounts make that risky.

How it works on the wall

  1. 1 · SubmitPaste your link and write what testers should look at.
  2. 2 · TestClaim someone else's project and write down what broke. That earns the credits that unlock your own reports.
  3. 3 · ReceiveMakers test yours and send a report, every problem listed with its severity.
  4. 4 · RateYou rate each other; both ratings unlock together.

Free, and based on reciprocity. The FAQ has every rule written out.

Questions

Why was my Google Play production access rejected after 14 days?
Most often because testers weren't engaged enough or the application didn't show what you learned from them. Meeting 12 testers for 14 days only makes you eligible to apply.
Do I have to restart the 14 days after a refusal?
Follow the instructions in the refusal email. In practice, expect to keep testing with engaged testers and ship improvements before applying again.
Do paid Google Play testers work?
They can deliver opt-ins. They rarely deliver engagement or feedback, which is what the production application asks about, and they put you in the pattern Google is trying to filter out.

Put yours on the wall.

Submit your project for free, test someone else’s, and get an honest report back.

Get your first testers