When does the 14-day clock start?

Per tester, from their opt-in. The 12 don't have to join on the same day, but there must be a 14-day stretch with 12 opted in at once.

Do I fail review if testers don't open the app?

No. Google counts opt-in time. In 44 measured runs testers averaged 8.5 open days and passed. The production form does ask about engagement, so zero opens is still a bad look.

It's been 14 days and the button is still locked

Check that 12 were opted in simultaneously for 14 consecutive days. A day where one person left and you were at 11 does not count.

Does internal testing count?

No. It has to be the Closed testing track. Internal testing is outside the requirement.

English · 한국어 · 日本語 · 简体中文 · 繁體中文

The 14 days of closed testing, as they really happen

Daily records from 44 finished tests

Google Play Console asks a new developer account for 12 testers, 14 days. One line of rules, and nothing about what to do during those days or what is actually being counted. On a board where developers trade tests, we kept the daily record of 44 finished runs.

Google counts opt-in time, not opens

The question is not whether a tester opened the app every day. It is whether they stayed opted in for 14 days. Skipping days does not hurt the review; leaving the test stops that person's clock. The evidence is in What Google actually checks.

Testers open the app on 8.5 of 14 days

That is the average across 44 runs. Only 2 of 44 testers opened it every single day. The drop-off comes early — day two or three — not at the end. People open it a couple of times out of curiosity and then forget. Full numbers: Nobody opens your app all 14 days.

Day by day

Day 1 — opt-in and install. Half of all problems live here: a link that opens nothing, a group nobody can join, a track with no build. Read the Google Group guide first.
Days 2–3 — the biggest drop-off. A tester with no reason to open the app disappears here.
Days 4–13 — quiet. As long as opt-ins hold, the requirement is being met.
Day 14 — the production button unlocks. Don't press it yet: read the 9 questions. Two of them decide the outcome.

If someone drops out

You do not start over. The others keep their days; a replacement only has to complete their own 14. But days when you are below 12 do not count, so 13 or 14 testers is the safe number. Why they leave is in Why testers disappear.

Making the 14 days feel short

Checking by hand whether testers open the app means trading screenshots for two weeks, and everyone tires of that. With ACT Party opening the other app records that day's check-in automatically. The developer sees who opened what on the board; the tester reports nothing.

Questions people ask

When does the 14-day clock start?: Per tester, from their opt-in. The 12 don't have to join on the same day, but there must be a 14-day stretch with 12 opted in at once.
Do I fail review if testers don't open the app?: No. Google counts opt-in time. In 44 measured runs testers averaged 8.5 open days and passed. The production form does ask about engagement, so zero opens is still a bad look.
It's been 14 days and the button is still locked: Check that 12 were opted in simultaneously for 14 consecutive days. A day where one person left and you were at 11 does not count.
Does internal testing count?: No. It has to be the Closed testing track. Internal testing is outside the requirement.

ACT Party lets developers trade tests and records the daily opens for you. Free. See the board · Get the app