How to keep closed testers active for all 14 days
Updated October 2026
Finding 12 testers is only half the job. Most of them install the app on day one, open it a few times, and then forget it. Google reviews whether testers really used your app, so a quiet second week can sink the whole test. These tactics keep people opening your app until day 14.
Why engagement matters
There are two hurdles. First, the 14-day clock only counts while at least 12 testers are opted in, so people leaving the test can stall your progress. Second, when you apply for production, Google reviews whether testers actually used the app during the test.
A list of 12 opted-in testers who stopped opening the app after day two meets the first hurdle on paper and fails the second. Engagement is what turns a closed test into a real test.
Practical tactics that keep testers coming back
- Recruit 14–15 testers, not 12. Someone always gets busy, changes phones or loses interest. The extra testers are your buffer.
- Give one concrete task per day. "Open the app" is easy to forget. "Today, create a list and share it" gives a reason to come back. A short checklist for the whole test works too.
- Push an update mid-test and say what changed. Upload a new build to the closed track around the end of week one and tell testers what's new and what to try.
- Ask for written feedback. Two or three specific questions get better answers than "any thoughts?". Reply, and fix what you can.
- Remind on day 3, day 7 and day 12. Day 3 catches people who never really started, day 7 restarts the second week, day 12 gets everyone over the finish line.
- Replace dropouts quickly. As soon as a tester goes quiet for a couple of days, invite a new one so you stay above 12.
A simple 14-day plan
- Day 1: welcome message, install link and the task list.
- Day 3: first reminder and a quick check of who hasn't opened the app.
- Days 5–8: upload a new build with fixes and announce what changed.
- Day 7: reminder plus a short feedback question.
- Day 12: final reminder and a request for written feedback.
- Day 14: thank your testers and note your numbers for the production application.
How Tester Exchange helps
- Daily use verified on phones: the Tester Exchange Android app checks on each tester's own phone that your app was opened that day.
- Daily report: see how many testers were active each day, plus the feedback they sent, so you spot dropouts early.
- Production answers: get draft answers for the production-access questions based on your real test data.
Google still makes the final decision on production access. These tools help you run a test that reflects real use and explain it clearly.
Frequently asked questions
My testers stopped opening the app. What should I do?
Message them with one specific task, push a small update so there's something new to try, and invite replacements right away for anyone who doesn't come back.
How often should testers open the app?
Google doesn't publish a number. Regular use by most testers across all 14 days is the safest pattern, and daily use is the clearest signal.
What happens if I drop below 12 testers?
The 14 days only count while at least 12 testers are opted in. Recruit 14–15 so a few dropouts don't stall your progress.
Should I really release an update during the test?
Yes. A new build that fixes reported issues shows Google that you used the test to improve the app, and it gives testers a reason to open it again.
Is written feedback required?
The production questionnaire asks what testers told you and what you changed. Written feedback gives you real examples to point to.