"I have 15 people on my tester list, but Play Console says I only have 9." It's one of the most common closed-testing problems — and it's almost never a bug. Being added to your list and counting toward the 12-tester requirement are two different things, and testers can fall off at several points in between.
What Google actually counts
- The requirement is at least 12 testers who have been opted in continuously for at least the last 14 days.
- Testers who opt in, test for fewer than 14 days, and then opt out don't count toward the requirement.
- If a tester opts out and opts back in later, the 14 days must be consecutive to count.
On this page
Invited isn't the same as counted
Every tester moves through four stages. Only the last one counts toward the requirement — and your tester list only tells you about the first.
- 1
Invited
Their Google Account is on your email list, or they've been given your Google Group address. Nothing has happened on their side yet.
- 2
Joined
For a Google Group, they've actually joined the group. Email-list testers skip this stage.
- 3
Opted in
They opened your opt-in link while signed in to the right account and accepted the invitation to become a tester.
- 4
Continuously opted in for 14 days
They've stayed opted in, without opting out, for at least the 14 days before you apply. This is the number that has to reach 12.
8 reasons a tester isn't counting
- They never opted in. Adding someone to your list doesn't opt them in. Each tester has to open the link and accept. If you're unsure, ask for a screenshot of the confirmation screen.
- They opted in with a different Google Account. Access is tied to the account on your list or in your group. A tester with personal and work accounts on one phone can easily accept with the wrong one.
- They didn't join the Google Group first. With Google Groups, testers must join the group before they can opt in to your test.
- They're opted in to your internal test. Google's documentation says a user who opts in to your internal test isn't eligible for an open or closed test — they have to opt out of the internal test first, then opt in to the closed one. See internal vs closed testing.
- They opted out — even briefly. Testers who opt out before 14 days don't count, and if they opt back in, their 14 days have to be consecutive again.
- The link wasn't live when they tried. The opt-in link only works once the track is Published, and after a first publish it can take several hours. Testers who tried too early and gave up never actually opted in.
- Their country isn't on the track. If a tester's country isn't in the track's countries/regions, they can't get the app from that track.
- The count hasn't refreshed yet. Google doesn't publish how often the Dashboard figure updates, and developers commonly report it lagging behind recent opt-ins. Give a new tester time before treating them as missing.
Does installing the app matter for the count?
Google's published requirement is about opt-in, not installs: it counts testers who are continuously opted in. By that wording, a tester who opted in but hasn't installed yet isn't excluded from the count.
That doesn't make installing optional in practice. When you apply for production access, Google reviews tester engagement and feedback — and a tester who never installed has neither. Our guide on why Google says more testing required covers what that review looks at.
How to find which testers aren't counting
- 1
Compare your lists
Write down who you invited and who has confirmed they opted in. The gap is your shortlist.
- 2
Check the account
Ask each missing tester which Google Account is active in their Play Store app, and compare it with your list.
- 3
Check your internal test
If you also run an internal test, check whether any closed testers are on it. They'll need to opt out of internal first.
- 4
Re-send the link
Send the Join on Android link again and ask them to open it while signed in to the listed account — and to confirm with a screenshot.
- 5
Top up if you need to
If you can't recover a tester quickly, add a new one. A new or re-joined tester starts their own run of 14 consecutive days, so do this early.
Prevent it on your next test
- Recruit more than 12, so one dropout doesn't push you under the minimum.
- Send testers a short checklist: which account to use, join the group (if you use one), open the link, accept, install.
- Keep your closed testers off your internal test.
- Only share the link once the track shows Published.
- Ask testers to stay opted in until you've applied for production access.
Our practice, not Google's rule
Google's minimum is 12. Our own service enrolls a buffer of testers above 12 for exactly the reasons above — so the requirement still holds if individual testers drop out.
Frequently asked questions
Why does Play Console show fewer testers than I invited?
Because it counts opted-in testers, not invited ones. Testers who haven't opened the link and accepted, accepted with a different Google Account, haven't joined your Google Group, or are opted in to your internal test won't be counted — even though they're on your list.
Does a tester count if they opt out and opt back in?
They can count again, but not straight away. Google says that if a tester opts out and opts back in later, the 14 days must be consecutive — so their 14 days effectively start over from when they re-joined.
Do testers need to install the app to count?
Google's published requirement counts testers who are continuously opted in, not installs. But Google also reviews engagement and feedback when you apply for production access, and a tester who never installed the app contributes neither — so in practice, they should install and use it.
Can I count myself as one of the 12 testers?
You can be one of them if you opt in to your own closed test like any other tester. You still need at least 12 in total, each continuously opted in for 14 days, and genuine use of the app matters when Google reviews your application.
How long does it take for a new tester to show up in Play Console?
Google doesn't publish a refresh interval for the Dashboard count. Developers commonly report a delay between a tester opting in and the number updating, so give it time — and confirm with the tester directly that they completed the opt-in.
If one tester drops out, do I have to restart the whole test?
Not necessarily. What matters is that at least 12 testers have been continuously opted in for the last 14 days when you apply. If you still have 12 who meet that, one dropout doesn't reset anything — which is why recruiting above 12 is worth it.
Official sources