TestFi Pro is liveSee ProOn Product Hunt today

TestFi Data

How long does real app testing take?

The average test session takes about 15 minutes from start to submit, and small campaigns complete in 1 to 3 days. Here is the timeline data from 1,758 real sessions.

~15 min
Average time per test, start to submit
< 24h
Typical first submissions
1-3 days
Typical 5-10 tester campaign
14 days
Google Play closed test clock

How long does a single test session take?

A real tester spends on average 15 minutes on a session, from pressing Start to submitting, measured across 1,758 submitted sessions on TestFi. That clock covers setting up the app as well as the test itself: the tester works through the developer's scenario while recording their screen and thinking aloud, then writes up what they found. End to end, most testers deliver their submission within 24 hours of accepting a campaign. This is meaningfully different from moderated usability studies, which typically require scheduling a 30 to 60 minute call per participant and coordinating calendars across time zones. In a marketplace model the sessions run in parallel and asynchronously: ten testers do not take ten times longer than one tester, they mostly finish within the same one-to-two-day window.

How fast does a full campaign complete?

Small campaigns of 5 to 10 testers typically complete within 1 to 3 days of going live. Submissions start arriving within hours because testers browse open campaigns continuously, and each session is AI-scored the moment it is submitted, so developers review results as they come in rather than waiting for the last tester. Larger campaigns scale roughly linearly with tester count. The practical bottleneck is usually the developer's review queue, not tester supply: each incoming session needs an approve-or-reject decision, and thoughtful developers watch the recordings before approving. Across 486 campaigns to date, the fastest pattern is a small first campaign, a fix cycle, then a retest with the same testers.

What about the Google Play 14-day closed testing requirement?

Google Play requires new personal developer accounts to run a closed test with at least 12 testers opted in for 14 consecutive days before the app can apply for production access. The 14 days is a fixed clock set by Google and cannot be shortened. What you can control is how fast the clock starts: it begins once 12 testers are opted in, so slow recruiting through swap groups or friends often adds one to two weeks before day one. On TestFi, 12 testers claim the seats within hours, and the median test reaches 12 confirmed installs in about 2.6 days (full closed testing data). See the full guide on the Google Play 12 testers requirement or read how to get 12 testers fast.

Methodology

All figures on this page are aggregates computed directly from TestFi's production database across 1,758 real test sessions submitted by paid human testers on real devices. Session quality is scored 0 to 100 by TestFi's 6-layer AI UX analysis engine before developer review. No individual user data is included, only aggregate statistics. Data last updated: 2026-11-20. You are welcome to cite these figures with attribution to TestFi (testfi.app).

Questions about the data? Contact contact@testfi.app.