The rule on the official page is short: at least 12 testers "opted in continuously for at least 14 days". Source: Play Console Help, retrieved 2026-10-17. This page turns it into a way to count.
The three statements from Google
- Testers must be opted in "continuously for at least 14 days".
- A tester who opts in, tests for fewer than 14 days and opts out "do[es] not count toward the requirement".
- If a tester opts out and back in, "the 14 days must be consecutive".
How to count your own days
- Day 1 is the day the tester opts in, not the day you create the test. (My reading; verify in your Console.)
- A tester counts only once their own run reaches 14 days.
- You need 12 such testers at the time you apply.
- Keep a log: tester (initials), opt-in date, opt-out date if any, day count.
Three timeline examples
Examples, with made-up dates. Day counts are my reading of the rule.
Tester A stays. Opts in on May 1 and is still in on May 15. Fourteen days reached, A counts.
Tester B leaves. Opts in on May 1, opts out on May 8. Seven days. Per Google, B does not count.
Tester C re-joins. Opts in May 1, out May 6, back in May 8. Google says the 14 days must be consecutive. So the earlier days probably do not add up; plan to count from May 8. Google does not spell out more than "consecutive", so this is the safe way to count.
Tips
- Tell testers up front to stay opted in for the whole period.
- Recruit more than 12 so one dropout does not reset your plan. See tester buffer and what happens when testers opt out.
- Add testers properly: how to add testers to a closed test.
AppReviewX test groups are built around 12 testers for 14 days in a row for Android apps; feedback is private and structured.