How to Create a Google Group for App Testing (Step-by-Step)

Before you can run closed testing on Google Play, you need a Google Group. The group acts as your tester list — only email addresses added to the group can join your closed test. This guide walks through setup from scratch, including the settings that catch people out.

What is a Google Group and why does Google Play need one?

A Google Group is an email list or discussion forum hosted by Google. For app testing purposes, you use it as an access control list. When you add someone's Gmail address to your group and they accept, they're eligible to opt in to your closed test via the Play Store opt-in link.

Google Play uses this as the authorization layer: if a tester's Google account is not in your group, they cannot join your closed test even if they have the opt-in link.

Step 1: Go to Google Groups

Open your browser and go to groups.google.com. Make sure you're signed in with the same Google account you use for Google Play Console. While it doesn't technically need to be the same account, mixing accounts causes confusion later.

Click "Create group" in the top left.

Step 2: Fill in the group details

You'll see a form with three fields:

• Group name — anything works. Use something descriptive like "MyApp Beta Testers" or just "testers". This name is visible to members.
• Group email — auto-filled from the group name. You can edit it. The email address doesn't matter for functionality.
• Group description — optional, can leave blank.

Click Next.

Step 3: Set the correct privacy settings

This step is where most people make mistakes. The settings that matter:

• Who can search for group — set to "Group members" or "Anyone on the web". Either works.
• Who can join group — set to "Only invited users". This ensures random people can't add themselves.
• Who can view conversations — doesn't matter for testing, set to "Group members".
• Who can post — doesn't matter, set to "Group managers" to keep things clean.

The critical setting is "Only invited users" for joining. This isn't required by Google Play — you can use other settings — but it prevents your tester group from filling up with spam accounts.

Click Create group.

Step 4: Add testers to the group

Once the group is created, you'll land on the group page. To add testers:

1. Click "People" in the left sidebar, then "Members"
2. Click "Add members"
3. Enter the Gmail addresses of your testers, one per line or comma-separated
4. Set role to "Member" (not owner or manager)
5. Make sure "Directly add members" is selected — this adds them without waiting for their acceptance
6. Click Add members

Alternatively, you can invite members, which sends them an email they must accept. Direct add is faster and more reliable for testing purposes.

Step 5: Connect the Google Group to Play Console

Now go to Google Play Console and navigate to Testing → Closed testing. If you haven't created a closed testing track yet, create one now (you can name it anything, like "Beta" or "Closed").

Under the track settings, find "Testers" and click "Manage testers". You'll see options to add a Google Group or Google Workspace domain. Click "Add email list" and paste in the email address of your Google Group (the one ending in @googlegroups.com).

Save the changes. Your testers are now authorized to join the closed test.

Step 6: Share the opt-in link

Being in the Google Group is not enough. Testers must also click the opt-in link and tap "Become a tester" on their Android device. The opt-in link is in Play Console under your closed testing track — look for "Tester opt-in URL" or a similar label.

Send testers both things:

1. A notification that they've been added to the Google Group (if you used "invite" instead of "direct add", they'll get an email)
2. The opt-in link, with a note to open it on their Android phone

Testers who try to open the opt-in link on desktop will see an error or won't be able to complete the process. The link must be opened on Android.

Common mistakes

Sending a Google Group invite link instead of an opt-in link

These are different links. The Google Group invite adds someone to your email list. The opt-in link (from Play Console) is what makes them an active tester. You need both, but the opt-in link is the one that actually matters for your 14-day counter.

Using a Google Workspace (work) account for testers

If a tester's Google account is a managed Workspace account (a corporate Google account), they may not be able to opt in to consumer app testing. This is a common issue when recruiting testers from within a company. Personal Gmail accounts work reliably; managed accounts often don't.

Adding too many people and running into the tester limit

A single closed testing track supports up to 2,000 testers. You won't hit this with 12 testers. But if you create multiple tracks and add the same group to all of them, testers might be confused about which opt-in link to use. Keep it simple: one track, one group.

The group exists but isn't linked to Play Console

Creating a Google Group doesn't automatically connect it to your app. You must explicitly add the group's email address in the Play Console tester settings. Check that the group email appears under "Email lists" in your closed testing track.

How to verify testers are active

In Play Console, go to Testing → Closed testing → your track. Under "Testers", you'll see a count of opt-ins. This is not real-time — it updates with a delay of a few hours. If you see 0 after a tester has opted in, wait a few hours and check again.

The 14-day counter appears in Publishing overview once you hit 12 active testers. If you don't see it, either the count hasn't reached 12 or Play Console hasn't updated yet.

Frequently asked questions

Related articles