Do Closed Testers Need to Open Your App Every Day?
Google requires 12 testers opted in for 14 days, not daily app opens. What the rule says, what reviewers look at, and how often testers should use the app.
Short answer
No. Google’s written rule is that 12 testers stay opted in continuously for at least 14 days. It does not say they must open the app daily. But the production access form asks how testers engaged with your app, so regular use (ideally most days) makes your application much stronger.
What the rule actually says
Google’s help page for new personal developer accounts says you must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. That is the whole eligibility condition. There is no published minimum for sessions, minutes or daily opens.
So a tester who opts in on day 1 and never opens the app still counts toward the 12 on Google’s counter. That is why the Play Console can show “14 days, 12 testers” for a test where nobody did anything.
Why daily use still matters
Meeting the counter only lets you apply. Approval depends on the production access questionnaire, which asks about your closed test: how you recruited testers, how they used your app, and what feedback you got and acted on. Developers who answer “testers installed it but rarely used it” are describing the weak kind of test the questionnaire is built to catch.
In our experience reviewing failed applications, the common pattern is a test that met the numbers but has no evidence of real use. That is our observation, not a published Google scoring rule.
A realistic target for testers
| Tester behaviour | Counts for the 12/14 rule? | Helps your application? |
|---|---|---|
| Opted in, never opened the app | Yes | No |
| Opened it on day 1 only | Yes | Barely |
| Used it a few minutes on most days | Yes | Yes |
| Used it most days and sent written feedback | Yes | Strongly |
Ask testers for a short session on most days and one or two written notes per week. That is enough to give you real crash data, real feedback and specific numbers for your answers.
How to get regular use without nagging
- Give testers two or three concrete tasks per session, not “please test my app”. See how to write testing instructions.
- Ship at least one update during the 14 days so there is something new to check.
- Reply to feedback quickly. Testers who see their bug fixed keep coming back.
- On TestersZone, testers check in daily with a timed session and feedback, so you get a dated log you can quote.
For the full engagement playbook, read how to keep closed testers engaged for 14 days.
Frequently asked questions
Does Google track how often testers open my app?
Google has not published what it measures. Play Console does show installs and Android vitals data for testing tracks, so assume reviewers can see whether the app was really used.
Will my test fail if a tester skips a day?
No. Skipping a day does not opt a tester out. Only opting out (or being removed from the list) breaks their continuous 14 days.
How long should each tester session be?
There’s no official minimum. A few minutes spent on a real task is far more useful than leaving the app open. Ask for one or two tasks per session so each visit produces something you can learn from.
What if testers only open it on weekends?
They still count toward the 12 as long as they stay opted in. For your application, weekend-only use is weaker evidence than regular use, so give those testers a reason to open it midweek, such as a new build to check.
Sources and how we keep this accurate
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
What Counts as an “Engaged” Closed Tester?
Does Google Check Whether Your Testers Actually Used the App?
How to Keep Closed Testers Engaged for 14 Days
Does Updating Your App Reset the 14-Day Closed Test?
A Tester Uninstalled Your App Mid-Test: Does It Still Count?
How Do Testers Leave a Closed Test (and What Happens)?
Browse all answers, or see the quick answers, guides and comparisons.