How to plan closed testing for a paid Android app.

Do closed testers have to pay?

Google’s testing documentation says testers normally purchase paid apps in open or closed tests. Internal testing allows installation of paid apps for free, but an internal test does not replace a required closed test. Read Google’s testing-track guidance.

Can I provide Google Play promo codes?

Google supports developer-created promotions that give access to paid apps. In Play Console, open Monetize with Play → Promo codes, choose Create promo code and follow the requirements shown for the promotion. Review the applicable terms yourself and choose the paid-app promotion type, dates and code count. One-time codes are redeemed once; subscription custom codes follow different rules. Google’s promo-code instructions.

Before distributing codes to a whole testing group, check one with the intended account, country and test track. Do not assume creating a code guarantees redemption for every release state. Keep the codes private and record who received each one. If redemption fails, capture the exact error and check availability and the current Play Console guidance.

What about in-app purchases and subscriptions?

Google provides licence testing for billing integrations. Configure the intended accounts under Settings → License testing and ensure they can access the correct release and test environment. Eligible test purchases let you exercise billing without treating every test as an ordinary customer purchase. Google’s licence-testing instructions.

Buying or redeeming access does not itself enrol someone in a closed test. Check both access and the testing invitation flow.

Check the full journey from invitation to paid features

A tester may be able to install your app and still be unable to reach the features you want checked. Confirm each layer before the group starts.

Run one complete check: invitation → opt-in → download → sign-in → agreed feature. If it fails, note the screen, build and error before inviting the whole group. See Google’s billing test guidance and our closed-test access troubleshooting guide.

In your enquiry, describe the access method rather than sending passwords or payment details. Request tester emails once you know which accounts need access.

Prepare a simple access plan

• State whether the initial download costs money.
• List any paid features needed for the agreed testing tasks.
• Confirm who supplies codes, test accounts or purchase funds.
• Test access before scheduling the full group.
• Record the app version and steps needed to reach paid features.

Never change app pricing or promise reimbursement casually just to start a test. Agree the access method and any costs before work begins.

Testing a paid app with Gigsdo

We can review your paid-access setup as part of scoping your test. Your final quote depends on app size, type, complexity and the work involved. Packages start from $29.99.