When a Google Play closed test drags, the natural thing is to blame the testers. Our numbers say it's mostly something else.
I run TestFi, which fills closed tests for developers on new personal Play accounts. Testers usually take all the seats within a couple of hours. Then each one goes through two hand-offs before they count: the developer adds their Gmail to the testers list in Play Console, and the tester installs from the opt-in link.
The numbers
I took the 85 closed tests that ran on TestFi in August and September 2026 and reached 12 confirmed installs, and split them by how long that took after the test went live. We count an install once we've checked the tester's proof.
| Time to 12 installs | Tests | Median time for the developer to add a tester's Gmail | Median time from added to installed |
|---|---|---|---|
| 3 days or less | 42 | 3.7 hours | 16.0 hours |
| 3 to 7 days | 21 | 19.2 hours | 19.4 hours |
| More than 7 days | 22 | 24.7 hours | 20.1 hours |
The install step hardly moves: testers took 16 to 20 hours whether the test was fast or slow. The difference sits in the first hand-off. In the fast tests, a tester's Gmail went onto the list in under four hours. In the slow ones it took a day, and that day comes back for every tester who arrives late.
The fix is boring. If you use an email list, check it twice a day and add people as they show up, not in one batch at the weekend. Or put a Google Group on the track: testers join the group themselves and the hand-off disappears.
Things that stop testers installing at all
Speed is one problem. A few setups block installs completely. Check these before you share the link:
- The link. The store listing link (it has
/store/apps/detailsin it) doesn't let anyone join a test. Testers need the opt-in link from your closed testing track, the one with/apps/testing/. - The release. If the build is still in review, or was never rolled out to the closed track, testers have nothing to install.
- Paid apps. Google Play charges everyone who installs a paid app, closed-test testers included. Make a promo code for each tester and send it with the link.
- Countries. If the track is limited to some countries, testers outside them can't install. Leave it open unless the app really doesn't work elsewhere.
- The Google account on the phone. Testers have to install with the exact Gmail you added. Anyone with two accounts on one phone runs into this.
- Device compatibility. A high minimum SDK or a device exclusion in the catalog quietly blocks some phones.
Before you share the link
- Opt-in link, not the store link.
- Release approved and rolled out to the closed track.
- Promo codes ready if the app costs money.
- Countries open.
- Someone checking the testers list twice a day, or a Google Group on the track.
None of this makes Google's 14 days shorter. It shortens everything around them, which is usually what turns a three-week job into five.
Disclosure: I'm the founder of TestFi. Our closed test puts 16 testers on your track for $39.99, or 20 for $49.99, and the campaign page lists each tester's Gmail as they arrive so you can paste it into Play Console straight away. Our public numbers are on the closed testing data page.
Hit something that isn't on this list? Tell me in the comments.
Top comments (0)