ClosedTestEveryone who runs a closed test worries about the same thing: will the testers actually keep going for two weeks? We looked at our own records to answer it with numbers instead of opinions.
What we measured, and what we did not
The numbers below come from ClosedTest's database on 26 October 2026. They cover completed runs only: 1,495 tester assignments (one tester assigned to one app for 14 days) and 16,942 daily check-ins.
Three things to know before you use these numbers:
- A check-in is not Google's opt-in. A check-in is a daily report recorded in our system, with a screenshot and an optional note. Google counts testers who are opted in to your closed test, as its testing requirements page explains. Check-ins are our measure of engagement, which Google also asks about. See tester engagement.
- Our testers are managed. They are recruited, paid and reminded every day. Friends and family who volunteer may behave differently, and we have not measured them.
- These are averages across many apps. Your own test could be better or worse.
How many days did each tester check in?
| Days with a check-in (out of 14) | Tester assignments | Share |
|---|---|---|
| All 14 days | 622 | 41.6% |
| 10 to 13 days | 576 | 38.5% |
| 5 to 9 days | 125 | 8.4% |
| 1 to 4 days | 85 | 5.7% |
| Never checked in | 87 | 5.8% |
Four in five assignments (80.1%) had a check-in on at least 10 of the 14 days. About one in nine (11.5%) contributed on four days or fewer, and that includes the 5.8% who never checked in at all. This happens even with paid testers and daily reminders.
What happened day by day
Check-ins per test day, across all completed runs:
| Test day | Check-ins | About this share of assignments |
|---|---|---|
| Day 1 | 1,066 | 71% |
| Day 2 | 1,107 | 74% |
| Day 3 | 1,119 | 75% |
| Day 4 | 1,168 | 78% |
| Day 5 | 1,167 | 78% |
| Day 6 | 1,172 | 78% |
| Day 7 | 1,211 | 81% |
| Day 8 | 1,222 | 82% |
| Day 9 | 1,247 | 83% |
| Day 10 | 1,254 | 84% |
| Day 11 | 1,275 | 85% |
| Day 12 | 1,300 | 87% |
| Day 13 | 1,313 | 88% |
| Day 14 | 1,321 | 88% |
The share column divides each day's check-ins by the 1,495 assignments, so it is approximate.
Check-ins did not fall over the 14 days. They rose: from 1,066 on day 1 to 1,321 on day 14, an increase of about 24%. We have not measured why. Two plausible reasons are that some testers start a day or two late, and that reminders and habit build up. We would rather tell you we do not know than invent an explanation.
What this means for your closed test
- Do not judge your test on day 1. Even in a managed process, only about 71% of assignments checked in on the first day. Check again on day 3.
- Expect some testers to contribute almost nothing. Roughly one in nine did four days or fewer. Plan a buffer. See how many testers to recruit.
- Replace early. A tester who has done nothing by day 3 rarely recovers. See what to do when a tester drops out.
- Daily habit matters. Short messages on day 3, 7 and 12 help. Use our message template.
Related data: which Android versions closed testers use.
Limits of this data
- It includes only completed runs, and the numbers change as more runs finish.
- Check-ins show engagement in our process, not what Google decides.
- We do not claim that these numbers predict approval. Google makes that decision.
You can see how these records appear in a report in our sample report (a fictional app) and on the testing results page.
ClosedTest is an independent service and is not affiliated with Google.