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 upload an install screenshot when they join, a check-in on day 3 and a short written report from day 12, 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.

Sources

Next steps

Still need testers? Get 12 testers for your closed test through a free test-for-test exchange - you test another developer's app, they test yours, and every opt-in is verified.

Common questions

Does a tester have to open my app every day to count?
No. The requirement counts testers who are opted in for the preceding 14 days, not how often they open the app.
Then why does engagement matter?
Because the production access application asks about it: how engaged testers were, whether they used all the app's features, and whether their use matched how real users will behave. Google can refuse access if the testing looks insufficient.
Does Google publish how it measures tester engagement?
No. Google publishes the questions it asks, not the signals it checks. Plan for testing you can describe honestly and in detail.

Apps currently in closed testing

Real developers running the test described above. Test one, and get testers for your own app back.

Closed testing

In Between is a free card game. Join the group, opt in, install, open it and play a hand. Keep it 14 days. Not available in South Korea. I test your app back the same day.

Games

Available in all countries

Open to testers · 14-day test

Closed testing

# BAYAA — Closed Testing: Instructions for Testers Thank you for participating in the BAYAA (بياع) closed testing program. BAYAA is a Mauritanian marketplace designed to connect customers with shops, restaurants, pharmacies, hotels, and service providers. ## 1. What testers are expected to do - Install BAYAA through the official Google Play closed-testing link. - Keep the app installed throughout the 14-day testing period. - Open and use the app regularly during the testing period. - Create an account and test registration and login. - Browse available shops, products, and services. - Test search and navigation. - Test merchant features if you have a merchant account. - Check WhatsApp contact options where available. - Report bugs, errors, confusing screens, and suggestions. ## 2. What feedback should you provide? Please tell us: - What worked correctly? - What did not work? - Were any pages slow or difficult to use? - Did you experience crashes or unexpected errors? - What features would you like us to improve? Honest feedback is very important. You do not need to give positive feedback if you encounter a problem. ## 3. Important testing rules - Use the app with your own tester account. - Do not share your login credentials. - Do not enter real payment or sensitive personal information. - Do not make fake purchases or transactions. - Do not uninstall the app during the testing period unless instructed. - Keep your Google Play testing enrollment active. ## 4. Reporting problems Send your feedback and screenshots of errors to the BAYAA development team. Thank you for helping us improve BAYAA and prepare it for its official launch in Mauritania. **BAYAA — بياع | Supporting Mauritanian Businesses**

Shopping

Available in all countries

Open to testers · 14-day test

Closed testing

PocketLedger helps you know your money and own your month — without handing your financial life to anyone. Everything stays on your phone. There is no account to create, no bank login, no SMS reading and no internet access at all. PocketLedger works fully offline. TRACK EVERY RUPEE (OR DOLLAR, EURO, POUND) • Add income and expenses in seconds, with category, account, date, merchant and notes • Mark refunds so they reduce your spending instead of counting as income • Search by merchant or note, filter by type, and tap any category to see its transactions for the month • INR, USD, EUR and GBP supported — amounts in different currencies are never mixed or converted SEE YOUR MONTH AT A GLANCE • Net cash flow, total income and total expenses for any month • Spending by category with an interactive chart • Recent transactions and account balances on one screen BUDGETS THAT KEEP YOU HONEST • Set a monthly limit for any category • See what you have spent, what is left, and when you go over ALL YOUR ACCOUNTS • Cash, bank accounts, UPI, credit cards and wallets • Pick from popular banks (SBI, HDFC, ICICI, Axis, Kotak and many more) and UPI apps, or type any name • Live balance for every account NOTHING IS EVER LOST • Every transaction keeps a full version history: see exactly what changed, when • Deleted transactions can be restored • An activity log records every add, edit, delete and setting change PRIVATE BY DESIGN • No sign-up, no ads, no tracking, no analytics • No internet permission — your data physically cannot leave the app • Not backed up to the cloud PocketLedger is a personal budgeting and expense-tracking tool. It does not offer loans, payments, banking or investment services and does not connect to any bank. Made by Technopreneurs Technolabs.

Finance

Available in all countries

Open to testers · 14-day test

Related guides

May we use analytics and ad measurement? Analytics (Vercel, and Ahrefs on our public pages) count page views without cookies. Ad measurement lets Google's tag on our public pages see which visits came from our Google ads, using a Google cookie. The site works the same either way. Cookie Policy · How Google uses data ·