Closed testing counts opt-in, not active daily use

Short answer: Google Play counts continuous closed-test opt-in for 14 days. Installing alone is not enough, and the help page does not require daily active use as a stated condition.

Google Play’s requirement is about continuous closed-test opt-in, not just installation. Testers need to stay opted in for 14 straight days, and the app must be installed for the test to count toward production access. The help page does not say they must open the app every day.

That is the part people get wrong. Installing the app once and leaving it there is not the same thing as meeting the testing requirement, because the requirement is tied to the closed test itself and the tester staying in the program for the full 14-day period. The safest reading is simple: opt in, keep the app installed, and keep the tester in the closed test without interruption.

Google’s Help Center says testers can install the test version after opting in, and that they must remain opted in continuously for at least 14 days. In the same help flow, Google explains that closed tests are distributed to users on your list or group and that testers receive the test app after they install it. That tells you what counts, and what does not.

The inconvenient part is that a tester who uninstalls, opts out, or is removed from the test before the 14 days are complete can break the count. If that happens, do not assume the clock still holds. Recheck the tester list and restart the closed-test period with the required number of testers staying in place for the full span.

If your goal is Production access for a new personal developer account, plan for more than the minimum. Google Play’s current requirement is 12 testers for 14 continuous days for personal accounts created after 13 November 2023. If a few testers drop off, you lose your margin fast, so recruiting a few extra real testers is the practical move.

A concrete example helps. If 12 people opt in on Monday, but only 10 of them are still opted in on the next Monday, the closed test does not satisfy the requirement yet. If all 12 stay opted in through the full 14 days, you have the period Google asks for, even if not every tester opens the app every single day.

That distinction matters because daily usage is harder to verify than opt-in status. Google’s own help page uses opt-in language, not a daily activity log, and the support community guidance points the same way. The requirement is not a public engagement metric, it is a closed-test participation window.

Do not try to replace real testers with paid tester services or bought installs. Google Play policy treats incentivized or inauthentic engagement as a violation, and that route can put the developer account at risk. DevConnect is built as an exchange on your own owned apps, not as a shortcut for fake participation.

If you are setting this up today, the clean process is: invite the testers, confirm each person opts in, confirm the app is installed on their device, and keep the closed test running for 14 uninterrupted days. If you want a place to coordinate that exchange, DevConnect keeps that work free and on owned projects only: https://devconnectplatform.com?ref=devto

If you are unsure whether a specific tester still counts, check two things first, did they remain opted in, and did they keep the test app installed through the full 14 days. If either answer is no, do not assume the requirement is satisfied.

For teams crossing over from Apple testing, the expectation is different. TestFlight allows external beta testers at a much larger scale and does not have the same 14-day closed-testing rule. Do not transfer Google Play assumptions onto Apple, or vice versa.

The short answer is this: installation alone is not the rule, continuous closed-test participation is. Active daily use is not stated as a requirement in Google’s help page, but the tester must stay opted in and keep the test app installed for the full 14 days.

What happens if a tester installs but never opens the app

Google’s published help focuses on opted-in status and the closed-testing period, not a daily open count. If you need production access, treat installation as necessary but not sufficient, and make sure the tester stays in the closed test for the full 14 days.

Does a tester have to reinstall if they leave the test

If a tester opts out or is removed before the 14 days finish, assume that participation no longer helps you. Add a replacement tester and restart your count carefully, because the requirement is continuous participation.

Does internal testing count toward the 14-day closed-test requirement

No. Internal testing is a separate track, with its own limit of up to 100 testers per app. It is useful for quick QA, but it does not replace the closed-test requirement for production access.

What should I do if I keep failing the closed-test check

Review the tester list for dropouts, missing installs, and people who never opted in correctly. Then restart with enough real testers to absorb churn, so you do not lose the full 14-day window because of one or two people leaving early.

Frequently asked

What happens if a tester installs but never opens the app

Does a tester have to reinstall if they leave the test

Does internal testing count toward the 14-day closed-test requirement

No. Internal testing is a separate track, with its own limit of up to 100 testers per app. It is useful for quick QA, but it does not replace the closed-test requirement for production access.

What should I do if I keep failing the closed-test check

Sources

Counting the 14 days yourself?
There is a free tracker for exactly that at
devconnectplatform.com/tools/closed-test-tracker.
No account, no signup, and the link keeps your progress.

Originally published at devconnectplatform.com, where it is kept up to date.