Google Play Closed Testing Guide: 12 Testers, 14 Days

Start with a testable build

Use this checklist to organise your first closed test. Before inviting a group, ask one person to install the build and complete its most important task. That small rehearsal can reveal a broken login or missing instruction before it affects everyone.

• Name the build and version code you want tested.
• Create a test account with access to the required screens. Share credentials privately.
• Write three tasks with an observable finish: create an item, edit it, and reopen it.
• Choose a private feedback channel and name the person who will answer access questions.

Configure the closed track in Play Console

Open your app in Play Console and go to Test and release → Testing → Closed testing. Select or create a track, prepare its release, and configure who can join. Google supports tester email lists and Google Groups. Follow the release status shown in Console before distributing access instructions.

1. Review the release and any outstanding setup tasks.
2. Check the intended countries and device eligibility.
3. Save the tester list or group and copy the opt-in link.
4. For a group-based test, explain how to join the group before opting in.

Send an invitation people can follow

Label the group link, opt-in link, and feedback link separately. Ask testers to use the invited Google account. An invitation should explain the app’s purpose and what to do after installing, rather than simply ask someone to keep the app on a phone.

Use a small testing brief

Illustrative example — a notes app, not a customer case study: “Create a note, add a tag, close the app, and reopen the note. Tell us whether the text and tag remain. Include the version, device model, expected result, and what actually happened.”

Adapt the tasks to your product. For a shopping app, inspect cart changes and checkout recovery. For a scheduling app, try editing and cancelling an appointment. Use sandbox transactions and test data wherever possible.

• Task: the action to perform.
• Expected result: what success looks like.
• Observation: what happened, including reproduction steps.
• Follow-up: owner, fixed build, and retest result.

Track participation and feedback separately

For personal accounts created after 13 November 2023, Google requires at least 12 testers opted in continuously for the preceding 14 days before applying for production access. Check your own Console for eligibility. An installation count is not a substitute for that requirement.

Keep a separate issue log so that meeting a participation threshold does not hide unresolved product problems. Record a tester’s observations without publishing their email address or private screenshots.

Close the test with a useful record

Group duplicate reports, identify fixes that were retested, and list remaining limitations. Preserve this record for the production application and your next release. The linked sample shows a possible format; its data is illustrative.