Keep Closed Test Running After Production Access?

Do I need to keep my closed test running after I apply for production access on a new personal developer account

Yes. Keep the closed test active after you apply for production access, because the application is based on an already qualifying closed test, and Google Play still needs that test track to remain valid while your request is reviewed. A new personal developer account created after 13 November 2023 must complete a closed test with at least 12 opted-in testers for 14 continuous days before it can apply for production access.

The part people get wrong is assuming the application freezes the requirement. It does not. The requirement is about the test being real, continuous, and eligible when Google Play evaluates it. If testers drop out, stop being opted in, or the closed test is ended before the account clears the requirement, the test no longer supports the production request. Google Play’s help pages say a user must stay opted in continuously for at least 14 days, and that you must meet Play’s criteria before applying for production access.

The inconvenient part is that the safest move is to leave the closed test running until you have production access and the app is actually rolling out. Google Play also notes that you can run multiple closed tests at the same time, and that internal testing is separate from the closed-test requirement, so you can keep a maintenance track alive without using it as a shortcut. Internal testing is for up to 100 testers and does not count toward the closed testing requirement.

Do not try to buy testers or installs to make the test look complete. Google Play prohibits manipulating ratings, reviews, or install counts with illegitimate or incentivized means, and it treats fake engagement as policy abuse. The safer route is simple exchange on your own assets, for example, test someone else’s app and have them test yours, without paying for participation. DevConnect’s model is built around that kind of reciprocal testing and nothing else.

If you are using DevConnect, the workflow is meant to support the real requirement, not replace it. You still need a closed test that stays qualified long enough to satisfy Google Play. DevConnect is useful for finding people who will actually install, keep the app opted in, and leave useful feedback, which is what the policy path is built around. You can start there: https://devconnectplatform.com.

A practical setup is to keep your closed test open, keep more than the minimum number of testers active so one or two drop-offs do not sink the count, and only stop the track after production access is approved and your public release is underway. Google Play’s current help page says the minimum is 12 testers for 14 continuous days for new personal accounts, while the older 20-tester rule is no longer current.

If a tester leaves early, uninstalling or dropping off can matter, because the requirement is continuous opted-in testing. That is why the safe operational answer is to keep the track live, monitor membership during the full window, and avoid any gap between your qualification period and your production rollout. The policy is designed to verify that the app was truly tested, not briefly staged for approval.

For Apple developers comparing the two systems, TestFlight works differently. Apple allows up to 10,000 external testers, and there is no Google Play style 14-day closed-test requirement. That difference is useful for planning, but it does not change the Google Play rule for a new personal account.

The short version is this: apply after you have a valid closed test, then keep that test running until production access is approved. Ending it early creates avoidable risk, and on a new personal account the hidden cost of a reset is time, not money.

FAQ

Can I stop the closed test as soon as I submit the production request

No. The request is based on a closed test that has already met the 12-tester, 14-day requirement, and the safest operational choice is to keep the test active until production access is granted and the rollout is in place.

Does internal testing count toward the 12 testers needed for production access

No. Google Play says internal testing is separate, supports up to 100 testers, and does not count toward the closed testing requirement for production access on a new personal account.

What happens if my tester count drops below 12 during the 14 days

The continuous closed-test requirement is no longer satisfied, so the qualification window can fail and the count can effectively reset. Google Play’s guidance is that testers must stay opted in continuously for at least 14 days.

Is buying testers a valid way to avoid a delay

No. Google Play prohibits illegitimate or incentivized engagement, including install-count manipulation. A reciprocal testing exchange on your own assets is the safe path, while paid tester schemes risk policy problems.

Do I need a bigger test group than 12

Google Play sets 12 as the minimum for qualifying production access on new personal accounts, but adding a buffer is operationally useful because testers can drop off before the 14-day window ends. That buffer is a practical safeguard, not a separate policy threshold.