Choose a Google Play testing track

You want someone else to try the app, and Play offers three testing tracks. Choose the one for the people who need access. If Google requires a closed test before production access, internal testing won’t count in its place.

Have a signed bundle, tester Google or Workspace accounts, and the setup required for your chosen track ready. Check whether your developer account can use open testing or production.

Pick a track

Track	Use it for
Internal testing	A small early group checking installation and core behavior.
Closed testing	A defined audience, including a required test for production access where applicable.
Open testing	A broader testing audience once you’re eligible and ready.

Release the build and invite testers

Create a release in that track, upload the bundle, add notes, and complete its review or rollout steps. Configure the tester list or group, then share the correct opt-in link.

Testers need to sign in with an eligible account and opt in before installing through the test route. Try the flow with a tester outside the developer account. Links and availability can take time to reach everyone.

A working test means an eligible tester can opt in, install the intended version, and give useful feedback. Collect that feedback and fix issues before expanding access.

If testers can’t install

Check the signed-in Google account, tester eligibility, released build, and track status.

Internal releases are often available quickly. However, the first fully configured release, or one following a rejection, can need review. Allow for that review when planning the test.

Use tester lists or groups to add coworkers. Managed Google Play organization distribution is a separate choice for private distribution. If production is locked, check the production-access requirements.