Do testers need to open your app every day during the closed test?
Updated
No, a tester does not have to open your app every day to count. The requirement counts testers who are opted in, continuously, for the fourteen days before you apply. A tester who opted in, installed the app and then forgot about it is still one of your twelve.
That answers the question about the count. It does not answer the question that decides whether you get production access.
What does Google actually count?
The rule, in Google's words: at least 12 testers "must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days." The things that break it are about the cohort, not about usage: a tester opting out, or the count dropping below twelve. See what happens if a tester opts out.
So why does engagement matter?
Because reaching twelve for fourteen days only lets you apply. The application then asks about your test, and Google reviews the answers. Among the things Google lists that the application asks about:
- the engagement you received from your testers,
- "whether testers used all available app features",
- "whether tester usage matched expected production user behavior",
- and a summary of the feedback they gave.
Twelve people who opted in and never opened the app give you nothing true to write in those answers. That is the practical reason daily use matters, even though the count does not require it.
Google does not publish the signals it uses to judge engagement, so nobody outside Google can tell you a number of sessions that is "enough". What you can control is having testing that is real and that you can describe.
What engagement should I aim for?
Think of how your real users will use the app, and ask testers to do that:
- Use the core feature more than once, on different days. A habit-tracker tested once on day one says little about day ten.
- Try everything, not just the first screen. Google's own advice to developers is to "encourage testers to use as many features as possible to provide holistic feedback."
- Send feedback you can quote. A short written note beats a thumbs-up. Set a feedback email or URL on the closed track so testers know where to send it.
- Ship a fix during the test and ask testers to try it. It gives you a change to describe in the production readiness section, and a new build does not reset anyone's fourteen days.
How do I get testers to keep coming back?
Tell them up front what you are asking for: how many days, roughly how often, and what you want them to look at. Specific requests get specific use.
On TestersWiz, testers submit screenshot check-ins on set days of the window, and each developer confirms the testers who held up their end, which builds their public reputation. That gives testers a reason to keep using the app, and gives you dated evidence of use to draw on when you answer the production access questions.
And if access was already refused?
Production access denied after closed testing covers what to check, and what to change, before you apply again.