How closed testing and Google Groups work

A closed testing track is a release channel only people you choose can join. Google’s requirement for new personal accounts is built on it. Most “testers cannot find my app” problems are track settings.

Tracks, in one paragraph

Play Console offers internal testing, closed testing and open testing. Internal testing is for up to a hundred people on your team and does not count for the twelve-tester requirement. Closed testing is the one that matters here. Open testing is public.

Two ways to choose testers

• An email list. You type or paste addresses. Simple, but every new tester means you edit the list.
• A Google Group. You add the group’s address to the track once; people join the group themselves, or you add them there. It is easier to grow and to share. A track can have several groups at once.

The opt-in link

Being on the list is not enough. Each tester opens the track’s opt-in link while signed in with the account that is on the list, and joins the test. Only then can they install from the Play Store, and only joined testers count. For a package called your.package.name the link has the form https://play.google.com/apps/testing/your.package.name.

Why testers see “app not found”

In our own testing, these are the usual causes:

1. The group or address is not on the track, or the tester joined with a different account.
2. The release is still a draft, or was never sent. A draft is not served to anyone.
3. A country is excluded. One missing country hides the app from every tester there. Cover every country available to you.
4. The release is in review. Until Google approves the changes, new testers may not see it yet.
5. Google has not applied a new group membership yet. This can take minutes.

A limit of Google’s API worth knowing

Google’s Play Developer API reports your saved configuration, including changes that have not been sent or approved. We measured the same output for an unsent draft, a change in review and an approved one. So a tool can tell you whether the group is on the track, a release exists and countries are covered, but not whether Google has made it visible. That is why TestersGuild calls an app “configured” after its check and “verified” only after real testers have installed it.

How TestersGuild uses groups

TestersGuild runs one Google Group shared by every cohort. You add that group’s address to your closed track next to any other groups you already have. It does not touch your other testers. Today you add it yourself; adding it automatically is coming. We read your track with a service account you invite with read-only access to one app, and we check that a group is present, a release is out of draft and 177 countries are covered (about; we update the list).