Play Console offers several testing tracks, and the names confuse a lot of new developers. The short version for a new personal account: only the closed test counts toward the production access requirement. This guide explains each track. It is based on Google's own help page.

The four tracks at a glance

Track	Purpose	What you need to use it
Internal testing	Quickly share builds with a small group of trusted testers and get early feedback	Nothing
Closed testing	Share your app with a group of users you control, to fix issues and check policy compliance before launch	Complete your app setup
Open testing	Show your test version on Google Play so anyone can join and send private feedback	Production access first
Production	Make your app available to everyone on Google Play	A closed test that meets Google's criteria, then an application

Internal testing

Internal testing is optional. Google describes it as a good starting point: builds reach testers within seconds, and you can use it before your app setup is complete. Use it to find the obvious problems early.

It does not replace the closed test. Google says you must run a closed test before applying for production.

Closed testing

This is the one that matters for a new personal account. Google says you must run a closed test before applying to publish, and that at least 12 testers must be opted in, continuously, for the preceding 14 days when you apply. You can start a closed test after completing your app setup.

You control who can join. That is why you invite testers by email list or Google Group. Read our 12-tester rule explained for what counts.

Open testing

Open testing becomes available after you gain production access. It puts your test version on Google Play so anyone can join, which is useful later for testing updates with real users. Before using it, check that your app and store listing are ready for public view.

Production

Production makes your app available to users. To reach it you need a closed test that meets Google's criteria, then you apply on the Dashboard and answer questions about your test, your app and your production readiness. See the production access questionnaire guide.

A simple order for a new developer

1. Use internal testing to catch obvious problems (optional).
2. Complete your app setup.
3. Run the closed test with at least 12 testers for 14 days, ideally with a buffer.
4. Collect feedback and fix what you find. Our 14-day plan shows how.
5. Apply for production access.
6. After you are live, use open testing or closed tests for future updates.

ClosedTest is an independent service and is not affiliated with Google.