Closed test testers dropped out: what to do now
A closed test rarely runs with the same 12 people from the first day to the last. Some opt out, some switch phones, some never opted in. Plan for it instead of reacting to it.
Spot the drop early
Open the closed test track in the Play Console and check the tester count and the days counted so far every day. A tester only counts after they accepted the opt-in link, so a long email list says little. Write the number down daily; you will want it for your production application.
Refill the same day
- Add new testers to the same Google Group or email list, not to a new track.
- Send them the opt-in link and ask them to confirm in a message once they have installed.
- Keep a reserve: 15 to 20 invited people for a 12-person minimum is a sensible buffer.
What happens to the 14 days
Google describes the requirement as testers who stay opted in for 14 days. Whether a dip below the minimum restarts the clock is not spelled out in the places we checked, and third-party guides disagree. Treat it as a risk: refill fast and read the current wording in Google Play Console Help.
Make dropouts less likely
Give each tester one small task per few days, such as finishing onboarding or trying the app offline. People who have something to do stay. Thank them by name when they report something useful.
Questions developers ask
Should I start over with a new track? Usually not. A new track means new opt-ins and a new count. Refill the existing one unless the Play Console tells you otherwise.
Do testers have to use the app daily? The requirement is about staying opted in. Regular use still makes your testing story much stronger when you apply for production access.
Need testers for your app? Open a test group on AppReviewX. Start free