A closed test lets a developer share an Android app with a chosen group before public release. When you join, you help the developer meet Google's requirement for testing before production access.
What Google requires of the developer
Google's help page says at least 12 testers must be opted in to the closed test when the developer applies for production access, and that testers must stay enrolled for a continuous 14 days. It also says testers who opt in, test for fewer than 14 days and then opt out do not count toward the requirement.
That is why your part is simple but matters: stay opted in for the whole period.
Steps
- Open the opt-in link the developer or the AppReviewX task gives you, on an Android device signed in with the Google account you want to test with.
- Opt in as a tester.
- Install the app from Google Play using the link provided.
- Keep the app installed and your account opted in for the full test period.
- Open and use the app, and send feedback.
Google's setup page says the opt-in link appears only once the app is published, that testers who click it must opt in, and that a Google Account is needed. The exact screens may differ; follow what Google Play shows you.
Feedback
Google says testers can send private feedback through Google Play. For AppReviewX tasks, write your structured feedback in AppReviewX as well: what you did, what you expected and what happened. Each feedback you write earns one credit.
Do not leave early
Opting out before day 14 can leave the developer short of the requirement. If you cannot continue, tell the developer in advance.
Testing is not rating. Nobody asks you for a public store review. See Testing apps is not trading ratings.
Back to Become an app beta tester: how it works. Related: How long should an app test take?, What makes tester feedback accepted. Developers: Google Play closed test requirements for new accounts.