A closed-testing package and a functionality-testing package solve two different problems. The first gets enough real people opted in and active so an affected Google Play account can apply for production access. The second tells you whether your app actually works when someone walks through it. Before you pay for either, check five things separately: official opt-ins, who owns continuity, real feature coverage, what feedback you get back, and the written remedy. Meeting the minimum lets you apply. It doesn't buy production access, because Google makes that call.
The mix-up usually happens at checkout, so here's the checklist I'd use if I were buying.
The rule you're actually buying against
For personal developer accounts created after November 13, 2023, Google asks for a closed test with at least 12 testers who stay opted in for 14 continuous days before you can apply for production. The details live in Google's help page on app testing requirements for new personal developer accounts.
Notice what that rule doesn't say. It doesn't ask whether your onboarding flow is clear or whether checkout crashes on Android 12. A run can satisfy the 14-day requirement while nobody ever opens your settings screen.
If what you need right now is the 12-tester requirement handled without chasing friends, that's what our 12 testers for 14 days setup at TestMyApps is built for. Keep reading if you're deciding whether you also need functional QA.
Coordination vs functionality QA, side by side
Two different jobs: keeping testers opted in, and checking the app actually works.
Coordination covers:
- Getting testers onto your closed track through the official opt-in link
- Checking each person is still opted in, day by day
- Replacing someone who drops out before it breaks your window
- Handing back notes you can use in the production-access questionnaire
Functionality QA covers:
- Walking defined user journeys, start to finish
- Recording expected vs actual results
- Reporting reproducible bugs with device and build details
- Retesting after you ship a fix
Both are useful. They're just not the same purchase, and a low price for the first one isn't a discount on the second.
Ask who tracks each tester, not just the daily total
A dashboard that says "12 active today" for 14 days in a row sounds fine. But if tester 7 left on day 5 and a new person joined on day 6, that new person hasn't been opted in for 14 continuous days. Daily totals hide that.
So ask the provider directly:
- Do you track opt-in status per tester, or only a total?
- When someone drops, do you replace them early enough that the replacement can still complete a continuous 14 days?
- Do you run with a buffer above 12 so one dropout doesn't reset your clock?
A provider who answers with "we'll make sure it's fine" hasn't answered.
What a useful QA report contains
The fields worth asking for before you pay for functional testing.
If you're paying for functionality testing, the report should let you reproduce every issue without a follow-up call. These are the fields I look for:
| Field | Why it matters |
|---|---|
| Build / version code | You know which upload was tested |
| Journey | e.g. "sign up with email, then add first item" |
| Expected result | What should have happened |
| Actual result | What did happen, with device and Android version |
| Issue reference | Something you can paste into your tracker |
| Changed build | The version where you shipped a fix |
| Retest result | Pass, fail, or not retested |
| Open risk | Anything still unresolved at closeout |
If a sample report has none of these and just says "app works great," that's coordination with a nicer label.
How we split it at TestMyApps
Since you're reading this on our account, here's our own offer so you can compare it fairly. Our standard packages are $15 for one app or $29 for two, with 14 testers over a 16-day window, daily opt-in checks and a closeout report for the production-access questionnaire. That's two testers and two days above Google's minimum, as a buffer.
The functionality packages are $50 for one app or $99 for two. Same 14 testers and 16 days, plus three end-to-end testing reports and regular feedback during the run.
If a run doesn't get you through, our guarantee is a free retest, and if it's still not approved, a refund. Google still decides production access, and nobody can promise that part.
Three questions before you pay anyone
- What exactly will I receive at the end? Ask for a sample report and check it against the table above.
- Who notices a dropout, and when? You want a named process, not "we monitor it."
- What happens if the run falls short? Get the remedy in writing before you pay.
And one warning that applies to every provider: never hand over your Play Console login. Nobody running a closed test needs it. You add testers through a Google Group or email list and share the opt-in link yourself.
A quick way to decide
- Your app is simple and you've tested it yourself on a few devices: coordination alone is usually enough.
- Your app has sign-in, payments, or several flows you haven't tested on other phones: pay for the functional reports too, or set up your own structured test.
- You're unsure: start with coordination and write down three journeys you'd want someone else to try. If you can't name three, you probably don't need the QA add-on yet.
When you're ready to start the 14-day clock, you can compare our packages on the TestMyApps 12 testers for 14 days page.
Top comments (0)