Closed Testing Tester Instructions: A Copy-Paste Template That Gets Real Feedback

Short answer: a good tester brief has five parts: what the app is, how to join, what to do each day, how to report problems, and a reminder to stay opted in for 14 days. Google recommends giving testers clear instructions and a clear feedback channel. Copy the template below and fill in the brackets.

Why most closed tests get thin feedback

Testers who receive only an opt-in link install the app, open it once and forget it. You end up with 12 names and nothing to write in the production access form, which asks whether testers used all the features and what they reported. A brief fixes that in five minutes.

The template

Subject: You're in! Testing [App name] for 14 days

Thanks for helping test [App name], an app that [one-sentence value].

How to join (2 minutes)

1. Open this link signed in with [the Google account you gave me]: [opt-in link]
2. Tap Become a tester, then install from Google Play.

Please stay opted in and keep the app installed for 14 days. If you leave early, Google doesn't count your testing.

What to try

• Day 1: sign up and complete [core action].
• Days 2 to 4: use [feature A] once a day.
• Days 5 to 7: try [feature B] and change a setting.
• Days 8 to 14: use the app as you normally would, and try anything you haven't tested yet.

How to report a problem
Tell us what you did, what you expected and what happened. A screenshot or screen recording helps a lot. Send it through Google Play's feedback or [form/chat link].

Thanks! We'll tell you what we fix.

Writing good daily tasks

Cover every feature at least once

The production form asks whether testers used all available features.

Mix guided tasks with free use

Guided tasks find bugs; free use shows whether real behaviour matches your expectations.

Keep each task under five minutes

Short tasks keep busy people engaged for two weeks.

Close the loop

Post a short update each time you ship a fix: "Version 1.0.2 fixes the crash on the settings screen that two of you reported." It keeps testers motivated and gives you a ready-made record of changes. TestLancer's guide to writing tester instructions has more examples.

The official rules, in one place

According to Google's Play Console Help article on app testing requirements for new personal developer accounts:

• The rule applies to personal developer accounts created after November 13, 2023.
• You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
• Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
• The application has three parts: About your closed test, About your app/game and About your production readiness.
• Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
• Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.

Quick checklist before you apply for production access

• [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
• [ ] A buffer of extra testers in case someone drops out at the last minute.
• [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
• [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
• [ ] A list of changes you made because of the test, with version numbers.
• [ ] Working test credentials in Play Console if your app needs a login.
• [ ] Content rating, target audience and data safety answers that match the real app.
• [ ] No crashes or empty screens on the build you're about to ship.

If any box is empty, a few more days of testing usually costs less than another review cycle.

Mistakes that cost developers extra weeks

1. Recruiting exactly 12. One opt-out and you're back to waiting.
2. Running the test on the internal track. Internal days don't count toward the requirement.
3. Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
4. Tidying the tester list mid-test. Removing someone ends their streak.
5. Shipping no updates. The production readiness section asks what you changed because of testing.
6. Using friends who never open the app. Google can ask for more testing when engagement is low.
7. Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.

FAQ

Should I pay friends to test?

Not required. A clear brief and quick fixes usually keep volunteers engaged.

Where should feedback go?

Use Google Play's private testing feedback plus one channel you check daily, such as a form or a chat group.

Can I translate the brief?

Yes. Testers who read it in their own language follow it more closely.

Next step

If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.