Android app testers opt in to your closed track, install the app, and then open it every day for fourteen days while telling you what breaks. The opting in is what Google counts. The opening every day is what makes the fortnight worth anything.
Most developers picture testers filing bug reports. In a closed test the job is simpler and stricter than that, and the part people underestimate is the daily part.
Here is exactly what happens across the fourteen days, and what to ask your testers for.
Updated September 2026
What does an Android app tester actually do?
Four things, in order.
- They opt in. They open your opt-in link and complete it with the same Google account that is on your tester list. This is the step that moves your counter.
- They install from the closed track. Not from a public listing, which does not exist yet.
- They open the app on most days. Fourteen days of real use, not one install and silence.
- They tell you what went wrong. Crashes, confusing screens, a button that does nothing on their phone.
Google only measures the first of those. Everything a reviewer later asks you about comes from the other three.
What happens day by day?
The shape of a fortnight that works.
| When | What testers are doing | What you should be doing |
|---|---|---|
| Day 0 | Opting in through your link | Checking the counter reads 12 or more |
| Days 1 to 3 | First run, sign-up, the obvious paths | Collecting the first crashes, which arrive early |
| Days 4 to 7 | Returning to the app, hitting the second screen and beyond | Shipping a fix, and telling testers you did |
| Days 8 to 13 | Longer use, saved data, notifications, updates | Writing down what they report, as it arrives |
| Day 14 | Still opted in | Applying, using your notes rather than your memory |
Why does daily use matter so much?
Because the bugs that matter do not appear on day one.
A first run is the most tested path in any app. The developer has walked it a hundred times.
What nobody has walked is day three, when a saved file loads wrong, or day ten, when an update lands on top of existing data.
There is a business reason too. When you apply, Google asks what your testers said, what you changed, and how you judged the app ready.
92.5% of the rejected apps that reach us failed because the testers went quiet. That leaves all three boxes empty.
What separates a real tester from a name on a list?
Activity, and nothing else.
Twelve email addresses on your tester list do nothing at all.
Twelve people who opted in and then stopped opening the app leave you in the same place. The counter satisfies Google, and you still cannot write the application.
This is also where policy sits. Real people on real Android devices are what Google asks for. Bulk-created accounts and emulators are what gets developer accounts shut down, which we cover in our post on the policy line.
What can Android app testers not do?
Worth being clear, because expectations here cause most of the disappointment.
- They are not a QA department. Closed testers use your app as people. They do not run regression suites or write test plans.
- They cannot fix your listing. Screenshots, description and store presence are separate work.
- They cannot approve your app. Production access is Google’s decision, and no service controls it.
- They cannot test what you have not built. A feature behind a flag they cannot reach will not be tested.
What should you ask your testers for?
Four requests, sent once at the start, save most of the trouble.
- Open it once a day, even for a minute. Say this explicitly. People who were asked to install will only install.
- Tell me the moment something looks wrong. Not at the end, when they will have forgotten.
- Say what phone you are on. A crash on one device and not another is the most useful report you will get.
- Tell me where you got stuck. Confusion is a bug, and it is the one developers never see themselves.
Frequently asked questions
What do Android app testers do?
They opt in to a closed track, install the app, use it across fourteen days, and report crashes and anything that fails on their device. The opt-in is what Google counts. The daily use produces the feedback you need for production access.
How many Android app testers do you need?
Google requires 12 opted in without a break for 14 days. Most developers arrange more than twelve, because one person opting out restarts the fourteen days.
Do Android app testers have to use the app every day?
Google does not require it. The production access form does, in effect, because it asks what testers reported and what you changed as a result. Without daily use there is nothing to put in those answers.
Can I use emulators instead of real Android testers?
No. Emulators are not real devices, and using them puts your developer account at risk. The test exists to show your app working on real hardware in real hands.
What is the difference between an app tester and a QA engineer?
A closed tester uses your app the way a customer would and tells you what broke. A QA engineer designs test cases, runs regression suites and works to a plan. Google’s requirement asks for the first.
How do I find Android app testers?
Friends with Android phones, a developer swap community, or a service that assigns them. Our Android app testers page explains how assigned testers work, and the free testers page covers the credit-based route.
Getting testers who actually open the app
Option 1: verified testers assigned to you
- Starter, $15 gives you 15 verified Android testers for the full 14 days.
- Pro, $25 gives you 25 testers, plus a detailed ASO report and priority support.
- Testers opt in within 6 hours, so your 14 days start today.
- Verified real Android devices, never emulators.
- Full 14-day retention. They open your app daily for the whole period.
- Automatic tester replacement if anyone goes inactive.
- A feedback report at the end, plus pre-filled answers for the production access questions.
- Production-access guarantee. Approved, or your money back.
This is what we do, and we are the best at it. We have been running Google Play closed tests since March 2024, longer than most services in this category.
More than 10,000 apps have reached production through the paid plans. Opt for a plan when you are ready.
Option 2: join a free Pack of 16
The Testers Community app pairs you into a pack of 16 developers, testing each other’s apps for 16 days. You earn credits by testing, then spend them on your own app. Inactive members are replaced.
Next, read the full requirements, our guide to inviting testers properly, and why testers need to open your app every day.
