Google Play

What Will My Testers See When I Invite Them?

Your testers see three screens: your link, a Become a tester page and the Play Store page. See how it normally goes, and how it goes with Testers Community.

November 19, 2026 · 10 min read
What Will My Testers See When I Invite Them?

Your testers see three screens: your message with the link, a Google Play page with a Become a tester button, and your app’s Play Store page with an Install button. Google does not send them anything. No email, no alert.

The screens are Google’s, so every tester sees the same three. What changes is who has to deal with them.

This post shows both ways. First how it normally works, when you invite people yourself. Then how it works with Testers Community, where we run this step every day.

Updated November 2026

The three screens, in order

Screen What the tester sees What they must do
1. Your message A link you sent by chat or email Tap it, in the right Google account
2. The opt-in page A Google Play page that says you invited them Tap Become a tester
3. The Play Store page Your app, with an Install button Tap Install, then open the app

Screen 2 is the one that counts. A tester who skips it is not in your test, even with the app on their phone.

How it normally works, and how it works with Testers Community

The screens stay the same. The work around them does not.

Step Normally, on your own With Testers Community
Finding testers You ask 12 or more people you know. We assign 15 or 25 verified testers within 6 hours.
Adding them in Play Console You type each email into a list. You add our Google Group to your track once.
Sending the link You message each person. You send one link to us.
Become a tester Some people close the page, and you chase them. Our testers tap it first, on every app.
Using the app for 14 days You remind people to keep using it. They use it for the full 14 days. Anyone who goes quiet is replaced.
When something is wrong The tester messages you, and you find the cause. Accounts and countries are sorted before testing starts.

Here is each screen, both ways.

Screen 1: your message, because Google sends nothing

Adding a tester in Play Console does not notify them. You copy the opt-in link from the Testers tab of your closed track. Then someone has to send it.

The Testers tab of a closed test in Google Play Console, showing an email list of 15 testers and the Copy link buttons testers use to join the test.
The Testers tab. The Copy link buttons give you the link your testers need.

Your testers cannot find the app by searching the Play Store. Google keeps a closed test out of search. The link is the only way in.

Normally: you send the link to each person yourself, by chat or email. Each one has to open it in the Google account you added.

If you use a Google Group, there is one more screen first. Each tester has to join the group before the link works. Google says so on its help page.

With Testers Community: you add our Google Group to your track once. Then you send one link to us, not 12 messages to 12 people.

Our testers are already in the group. We give your link to the testers assigned to your app.

Screen 2: the opt-in page

This is a plain Google Play web page with your app name, your developer name, a short note and one button. It opens in the phone’s browser.

The Google Play opt-in page on a phone. It shows the app name and developer name, a note that the developer has invited you to a testing program for an unreleased version, a warning that testing versions may be unstable, a feedback contact, and a Become a tester button.
The opt-in page, as a tester sees it on a phone. Example app shown.

Here is what each part tells your tester.

On the page What it means
Your app name and developer name The tester sees the developer name from your Play Console account.
You are invited to a testing program for an unreleased version They know it is a test, not a finished app.
Testing versions may be unstable Google warns them to expect bugs.
Data on your use of the app is shared with the developer Google tells them you can see how the app is used.
Send your feedback to this contact This is the feedback email or link you typed in Play Console. Testers can see it, so pick one you are happy to show.
Become a tester The step that puts them in your test.

After the tap, the page confirms they are a tester and points them to Google Play to get the app.

Normally: this is where first-time testers stop. The page reads like a notice, so people close it without tapping the button.

Nothing tells you this happened. You only see that your opted-in count stays low.

With Testers Community: our testers do this step on every app we test. Become a tester is the first thing they tap.

Screen 3: the Play Store page

The tester lands on your app’s Play Store page and taps Install. It installs like any other app.

A few things are different from a public app:

  • No public review. Google does not let testers post public reviews on a test version.
  • Private feedback instead. Testers can write feedback in Google Play that only you can see.
  • The price, if your app is paid. In a closed test, testers pay for a paid app like anyone else.

Updates need no new link. Google says a tester’s app updates to your newest test version on its own.

Normally: a friend installs the app, opens it once and forgets it. You have to remind people to keep using it for 14 days.

With Testers Community: our testers install on real Android devices and use the app for the full 14 days. Anyone who goes quiet is replaced. At the end you get a feedback report.

What testers see when something is wrong

What the tester sees The usual cause
A message that the app is not available They opened the link in a different Google account, or they have not joined your Google Group yet.
The link opens nothing useful Your first release is still in review. After that, Google says the link can take several hours to work.
No results when they search the Play Store Normal. A closed test is not in search. They need the link.
A price on the Install button Your app is paid.

Normally: each row is a message from a confused friend, and you work out the cause. Our guide to a tester who cannot find your app walks through each fix.

With Testers Community: most of these rows never reach you. Accounts and countries are sorted before testing starts, and our testers already know the opt-in step.

One row stays yours: the release. Google has to finish its review before any link works, for any tester.

How does the testing step work with Testers Community?

Production access, or your money back.

  1. Go to testerscommunity.com/submit-app and submit your app.
  2. Opt for Starter, $15, paid once for that app.
  3. That is all.

We assign verified testers on real Android devices within 6 hours. They open your link, tap Become a tester, install the app and use it for the full 14 days. Anyone who goes quiet is replaced.

At the end you get a feedback report, and we help you write the production access answers. You submit the application, and Google makes the decision.

More than 20,000 apps have gone live through our paid plans.

Six jobs you handle when recruiting testers on your own, each matched to what Testers Community does: assigns verified testers, testers know the opt-in step, inactive testers are replaced, accounts and countries handled before testing, a feedback report, and help writing the production access answers.
What you handle on your own, and what Testers Community handles for you.

Frequently asked questions

Does Google email my testers when I add them?

No. Adding a tester in Play Console sends them nothing. You have to send the opt-in link yourself.

Can my testers just search for my app on the Play Store?

No. An app in a closed test does not appear in Play Store search. Testers need your opt-in link.

What do my testers have to tap?

Two buttons. Become a tester on the opt-in page, then Install on the Play Store page.

Do Testers Community testers see different screens?

No. They see the same Google Play screens as any tester. The difference is that they have done the opt-in step before, and we handle the link, the accounts and the follow-up.

Will my testers know the app is a test version?

Yes. The opt-in page says it is an unreleased version and warns that testing versions may be unstable.

Can my testers see my email address?

They see your developer name and the feedback contact you entered in Play Console. If that contact is an email address, testers can see it.

Can my testers leave a review?

Not a public one. Testers can send private feedback through Google Play, and only you can read it.

Do my testers get updates automatically?

Yes. Once the app is installed, it updates to your newest test version without a new link.

Run your testing step with Testers Community

  • Production access, or your money back.
  • Starter, $15 gives you 15 verified Android testers for the full 14 days. Paid once per app.
  • Pro, $25 gives you 25 testers, plus a detailed ASO report and priority support. Also paid once per app.
  • A feedback report at the end, plus help with the production access answers.

Submit your app and opt for Starter when your build is ready.

Short on budget? The free Pack of 16 in the Testers Community app has developers test each other’s apps for 16 days.

Related: how to invite testers to a closed test.

Sources

  1. Play Console Help: Set up an open, closed, or internal test.
  2. Google Play Help: Try new Android apps before their official release.
  3. Google Play Console: Closed testing.

You might also like

Trusted by 20,000+ apps

Ready to publish your app?

Get Google Play production access with real testers, guaranteed results, and expert support every step of the way.

25 professional testers
Production access guarantee
16-day testing (2 days buffer)
24/7 expert support
Get Started