License testers and closed testers are two separate lists in Play Console with different jobs. License testers, set under Settings > License testing, can test in-app purchases and subscriptions without being charged real money. Closed testers are the people on your closed testing track who opt in and get your test build, and they're the only ones who count toward the 12-tester, 14-day requirement. Adding someone as a license tester doesn't make them a closed tester, and the reverse is also true.
What license testers are for
Google's help page Test in-app billing with application licensing describes license testers as accounts you authorize to test billing. It says authorized users "can also purchase one-time products and subscriptions without charging their accounts."
The Android developer documentation on testing Google Play Billing adds the detail: "License testers have access to test payment methods that avoid charging the testers real money for purchases. You can also use test payment methods to simulate certain situations, such as when a payment is declined." It also notes that test subscriptions renew much faster than real ones, so you can test renewals in minutes instead of months.
In short, license testing is about payments. It lets you and your team check that purchase flows, subscriptions and declined payments behave correctly before real money is involved.
What closed testers are for
Closed testers are the people you invite to a closed testing track, through an email list or a Google Group. They open the opt-in link, accept the invitation and install the test build from Google Play.
For new personal developer accounts, closed testers are also how you meet Google's requirement to "run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days." What counts as an opted-in tester explains that count in detail.
Closed testing is about distribution and real use: getting a pre-release build to real people and learning from how they use it.
Side by side
| License testers | Closed testers | |
|---|---|---|
| Where you set them | Settings > License testing (account level) | The closed track's Testers tab (per app, per track) |
| How you add them | Email lists or Google Groups | Email lists or Google Groups |
| Main purpose | Test purchases and subscriptions without real charges | Get test builds and give feedback |
| Do they need to opt in? | Not as license testers, but to get a test build they must also join a test track | Yes, through the opt-in link |
| Count toward the 12-tester rule? | No, not by being license testers | Yes, if opted in continuously for 14 days |
How the two lists work together
License testing doesn't deliver your app to anyone. For a license tester to test billing in a release from Google Play, Google's help page says the app must be "published to the open, closed, internal test, or production track", and you should "make sure that your testers are also eligible to receive your release."
So a typical setup for an app with in-app purchases looks like this:
- Add your team and a few trusted testers to Settings > License testing.
- Add the same people, plus everyone else, to your closed track's tester list.
- Each person opts in to the closed test using the opt-in link.
- When license testers buy something in the test build, they see test payment methods; other closed testers go through the normal purchase flow.
The developer documentation also says license testers can test billing in sideloaded or debug builds, as long as "the package name must match that of the app that is configured for Google Play, and the Google Account must be a license tester." That's useful for development, but it has nothing to do with the closed test count.
Mistakes to avoid
Thinking license testers count toward the 12
They don't, at least not because they're license testers. Only people who opt in to your closed test count. If your 12 testers are only on the license testing list, your closed test has zero opted-in testers. Check your closed track's tester list instead. Email list or Google Group compares the two ways to add them.
Making every closed tester a license tester
It can seem convenient, but think it through. The production access form asks whether tester usage matched expected production behavior. License testers pay with test payment methods, so their purchases tell you nothing about real checkout problems and bring in no real revenue. It's usually better to keep license testing to your team and a small group who check payments specifically.
Expecting a license tester to get the app without joining a track
License testing is an account-level setting. It doesn't attach anyone to a release. Testers still need to be eligible for a track and, for closed tests, opt in.
Confusing it with internal testing
Internal testing is a third, separate thing: a track for up to 100 testers that also doesn't count toward the requirement. See internal, closed and open testing for how the tracks differ.
A quick setup check
- Team members who test payments are on Settings > License testing
- All testers, including the team, are on the closed track's tester list
- Everyone has opted in through the closed testing link
- At least 12 testers opted in for 14 continuous days if you need to meet the requirement
- Purchase flows tested with test payment methods before you apply
Key takeaways
- License testers test billing without real charges; closed testers receive and test your build.
- They're configured in different places and serve different goals.
- Only opted-in closed testers count toward 12 testers for 14 days.
- Apps with purchases usually need both lists, with license testing kept to a small group.
Once billing works and your closed track is live, our setup guide shows how to add GoPlayTester's tester group to the closed track if you need testers, and the production access guide covers what to do after the 14 days.
