Closed testing testers not counted: why Google sees fewer than 12
You invited 15 people. Maybe 20. Google still says your app needs more testing, or your own count doesn't add up. There's no error message for this. The cause is almost always the same: the people you think of as "testers" aren't all opted in to the closed test, continuously, for the 14 days before you apply.
Here's 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" (Play Console Help). Every word in that sentence is a way to lose testers.
One tester missing, or many?
| Pattern | Likely cause | Check first |
|---|---|---|
| A whole batch of testers never counted | They're on the wrong track, or never opted in | Causes 1 to 3 |
| One or two testers dropped | They left, or joined late | Causes 4 and 5 |
| Count looked fine, Google still asked for more testing | Activity, not headcount | Cause 7 |
Causes and fixes, in the order to check them
1. They're in your internal test, not your closed test
Only a closed test meets the requirement. Google's track table lists internal testing with no requirement and production behind "a closed test with at least 12 opted-in testers" (Play Console Help).
Worse, internal testing blocks the closed test. Google says: "A user who opts into your app's internal test is no longer eligible to receive an open or closed test" (Play Console Help).
Fix: remove your closed testers from the internal list. Ask them to leave the internal test, then opt in to the closed test. Their 14 days start from that opt-in. The differences between the three tracks are laid out in internal vs closed vs open testing.
2. They're on the list but never opted in
Adding an address to an email list, or a person to your Google Group, only lets them in. It doesn't opt them in. Google says testers get an explanation of tester responsibilities "and a link to opt in. Each tester needs to opt in using the link" (Play Console Help).
Fix: send the opt-in link again to anyone who hasn't confirmed. Ask each tester for a screenshot of the page that says they're a tester, with the date. That's your proof.
3. Your group or list isn't attached to the right track
Testers belong to a track through the list or group you set on its Testers tab. If you created an additional closed track, it has its own testers. If your Google Group was typed into the wrong field, nobody in it is on the track.
Fix: open Test and release > Testing > Closed testing > Manage track > Testers on the track that has your release. Check that the Google Group is entered with the Google Groups option, or that the right email lists are ticked, and that you saved. Google doesn't say whether testers spread across several closed tracks are added up. Keep your testers on one track.
4. Testers left the test
A tester can leave at any time. In the Play Store app, testers find your app under Manage apps & devices > Beta and tap Leave (Google Play Help). Some do it to get rid of a buggy build. Some do it by accident.
Google's FAQ is strict: testers who opt in, test for fewer than 14 days and then opt out don't count. "If a tester opts out and opts back in later, the 14 days must be consecutive to count toward the minimum requirement" (Play Console Help).
Fix: a tester who left and came back restarts at day 1. Recruit a replacement early rather than waiting for them to reach 14 days again.
5. You counted 14 days from the start of the test, not per tester
Each tester has their own 14 days. If eight people opted in on day 1 and four more on day 5, you have 12 testers with 14 consecutive days only from day 19, not day 15. More on how this adds up in how the 14 days are counted.
Fix: keep a simple log: tester address, opt-in date, still opted in (yes/no). Your earliest application date is 14 full days after the opt-in of your 12th tester, as long as none of the first 12 left.
6. You changed the list or the group during the test
Google's help pages don't say what happens to a tester's opt-in when you remove their address from the list, or remove them from the group, in the middle of the test. Don't find out the hard way. Avoid "cleaning up" your list or group until you have production access.
7. The headcount was fine, the activity wasn't
When Google asks for more testing, it gives two kinds of reasons: "having fewer than 12 opted-in testers or insufficient tester engagement during the testing period" (Play Console Help). Opting in is the rule. Using the app is what the form asks about: whether testers used all features, and whether their usage matched what you expect in production.
So 12 people who opted in on day 1 and never opened the app may be counted, and still not be enough. If that's what happened, see production access rejected.
Build a margin from day 1
- Recruit more than 12. People drop out. Start with 15 to 20 and you can lose a few without restarting the clock.
- Tell testers the rule. Google itself recommends you "inform your testers that they need to remain opted in to your closed test continuously for at least 14 days" (Play Console Help).
- Keep your own records. Google's help pages don't describe a per-tester opt-in report you can export. Your log and the testers' screenshots are what you'll rely on.
- Don't apply on the first possible day. One late tester or a timezone shift can leave you a day short. Applying a day later costs little.
When to contact Google
If your records show 12 or more testers opted in to the closed test, continuously, for the 14 days before you applied, and Google still told you there were fewer than 12, use the Contact us link in Play Console Help. Attach your log and the testers' dated screenshots. For everything else, the answer is more testing time, not support.
For the full picture of the requirement, see the Google Play closed testing guide.
Frequently asked questions
Do internal testers count toward the 12 testers?
No. Google requires a closed test with at least 12 testers. Internal testing is a separate track, and Google says someone who opts into your internal test is no longer eligible for your closed test.
Does a tester who opts out and rejoins still count?
Only from the day they rejoin. Google says that if a tester opts out and opts back in later, the 14 days must be consecutive to count.
Is adding a tester's email to my list enough?
No. Being on the list or in the Google Group only allows them in. Each tester must open the opt-in link and opt in.
Do testers need to keep using the app?
Google's rule is about staying opted in for 14 days. But Google also lists insufficient tester activity as a reason to ask for more testing, so testers should keep using the app.