What to Send 12testers Before Your Managed Closed Test Starts

A managed run starts cleanly when the handoff proves which release to join, who can access it, how testers reach the core workflow, and what evidence the developer needs at closeout.

A complete handoff protects the start date

12testers can coordinate people and devices only after the release path is usable. A package name without a published closed-track release is not enough, and a Play Console screenshot does not let a tester join.

Treat the handoff as a release-readiness checkpoint. The goal is to remove ambiguity before anyone begins: one app, one intended track, one official opt-in route, one access method, and a short list of workflows that matter.

Send the release identity and tester route

Begin with the public-facing app name, Android package name, closed-track name, release version or version code, and the web opt-in URL copied from that track. These values allow support to distinguish the intended build from an older test or production listing.

State whether access uses an email list or a Google Group. If it uses a group, include the group address and membership route. Google’s setup guidance requires group-based testers to join the group before they can opt in.

Map the handoff from release to ready

Run a single-device access rehearsal before the managed cohort begins. Use an authorized account to join, open the Play Store link, install or update the intended version, and reach the first meaningful screen.

If that rehearsal fails, stop at the failed checkpoint rather than sending more invitations. Fixing the release state or authorization route first prevents a false start across the entire cohort.

Provide safe app access without sharing personal credentials

If the app requires sign-in, create limited test accounts that expose only non-sensitive sample data. Document the login path, any role selection, and whether an OTP, invite code, subscription state, or backend allowlist is involved.

Never send a Google account password, Play Console login, payment credential, or private production customer data. 12testers needs access to the app experience, not ownership of the developer account.

Define the app-specific work and evidence you need

Choose three to five workflows that represent the release. A finance tool might prioritize onboarding, a sample calculation, export, and account deletion. A marketplace might prioritize browsing, search, a test checkout path, notifications, and support.

Explain any destructive actions to avoid and what a useful issue report should include. Device model, Android version, app version, steps, expected result, actual result, and a screenshot usually make a finding reproducible.

Use a clear go or hold decision

Mark the handoff ready only after the release is available, the intended tester identity can opt in, installation succeeds from Google Play, required app credentials work, and the priority workflows are understood.

If any item is still unknown, hold the scheduled start and name the owner of the fix. A short delay before the run is safer than discovering an access blocker after the continuity window was supposed to begin.

What is the most important link to send 12testers?

Send the official web opt-in URL copied from the exact closed track that contains the intended release. A Play Console dashboard URL or APK download is not a substitute.

Should I send my Play Console password?

No. Never share a personal Google password, verification code, or Play Console login. Provide only the release details, tester authorization route, and limited app-specific test credentials needed for the test.

Can the run start while the release is pending publication?

No. Google states that the opt-in link is shown only when an app is Published. Wait until the closed release is available and verify it with an authorized account.

What if my app needs an OTP or manual account approval?

Describe the process before scheduling and provide a safe operating method for every assigned tester. Test the process end to end on one authorized device first.