Closed, open or internal testing: which track?
Choose the track for the question you need answered. Can your team install the build? Can invited users finish real tasks? Is the app ready for a public test? Those are different stages.
Compare the tracks
| Track | Who joins | A useful purpose |
|---|---|---|
| Internal | Up to 100 chosen testers | Check installation and obvious faults |
| Closed | Your chosen tester lists or groups | Observe invited users doing real tasks |
| Open | Anyone; the test is visible on Google Play | Gather feedback from a wider audience |
These access differences come from Google's track guide. The suggested purposes are our planning advice.
For new personal accounts covered by the testing requirement, internal testing does not replace closed testing. Open testing unlocks after production access. Google's account requirements.
Choose the next step
- You have only run it on your own phone. Start with a small trusted group. Ask someone to install it and complete the main task without your help.
- Play Console asks for a closed test. Plan recruitment, tasks and feedback collection together. Use the closed-testing checklist.
- You want a broader test audience. Prepare clear onboarding, an accurate listing and a way to handle incoming feedback before opening the doors.
Do not choose a track just because a tutorial uses it. Write down what you need to learn from this build first.
Give testers a clear handover
Send the intended track, install link, build label and first task together. Ask testers to include their installed version when reporting a bug. That saves you from comparing reports about different builds.
For a paid app, closed and open testers must buy it; internal testers can install it free. Google's paid-app testing rule. Explain any cost before inviting someone.