deepwall
HomeContact UsLogin
  • Overview
  • System Components
  • Key Concepts
  • How It Works
  • Sign In
  • ๐Ÿš€GETTING STARTED
  • App Registration
  • Configure In-App Products
  • Paywall Setup
    • Create A Paywall
    • Configure Look & Feel
    • Texts and Translations
  • Displaying Paywalls
    • Activate Default Displays
    • Create Targeted Displays
    • Display Priorities
    • Display Reports
    • Edit Displays
    • Display Rules
    • On Close Paywalls
  • Store Configuration
  • Attributions Configuration
  • App Status and Settings
  • โš™๏ธ SDK Framework
    • SDK Installation
      • iOS SDK
      • Android SDK
      • React Native SDK
      • Flutter SDK
      • Cordova SDK
      • Unity SDK
    • Using the SDKs
      • Initialization
      • Configuration
      • Listening SDK Events
      • Requesting Paywalls
      • Closing a Paywall
      • Validating Receipts
      • Making Purchases
      • Upgrades and Downgrades
      • Non-subscription Purchases
      • Restoring Purchases
      • Transition To Another Paywall
  • ๐ŸงชEXPERIMENTS
    • Experiments Overview
    • Create Experiments
    • Experiment Reports
    • Manual Traffic Allocation
    • Update Experiments
    • How Optimization Works?
  • ๐Ÿ“ฆIntegrations
    • Integrations Overview
    • Events List
    • Adjust
      • Get App Token
      • Create Adjust Events
    • AppsFlyer
      • Get Dev Key
    • Webhooks
    • OneSignal
  • ๏ฃฟ App Tracking (iOS 14.5)
    • App Tracking Overview
    • Configure In-app Actions
    • Create ATT Prompt
    • Displaying ATT Prompts
    • Experiments
  • ๐Ÿ“ˆDASHBOARD
    • App Overview
    • Invite Members
    • Access Management
  • GUIDES
    • Apple
      • Getting the App Credentials
      • Setup In-App Products
      • Getting the Shared Secret
      • Server to server notifications
    • Google
      • Getting App Credentials
      • Setup In-App Products
      • Create Service Account Key
      • Developer Notifications
    • Huawei
      • Getting App Credentials
      • Setup In-App Products
      • Developer Notifications
  • ๐Ÿ”Testing
    • Test Flows
    • Troubleshooting
    • Sandbox Testing
      • Apple App Store
      • Google Play Store
  • ๐Ÿ”—SDK Links
  • iOS SDK
  • Android SDK
  • React Native SDK
  • Flutter SDK
  • Cordova SDK
  • Unity SDK
Powered by GitBook
On this page
  • Sandbox Test User Account Creation
  • Closed Track Creation & Add Testers
  • Adding a Signed Version to the Closed Track
  • Testing on Android Devices

Was this helpful?

  1. Testing
  2. Sandbox Testing

Google Play Store

PreviousApple App Store

Last updated 4 years ago

Was this helpful?

We ensure successful testing on the emulator, but Google recommends using a real device. If you are using an emulator, make sure that Google Play Services is installed on it.

Sandbox Test User Account Creation

You will need to use a test user account to be able to test the application. This tester will be the first user to sign in to your Android Tester. Note that the only way to change the primary account on a device is to reset it to factory settings. Add the account you use on your actual device here by following the steps below:

  • Log into your account on Google Play Console.

  • Click License testing under Settings on the left side.

  • Register your test user accounts by entering them in the Add license testers field.

Closed Track Creation & Add Testers

You will need to release a signed version of the app on a closed channel. If you haven't created a closed channel yet, you should follow the steps below to create it:

  • Log into your account on Google Play Console.

  • Select your app and go to details.

  • Click Closed testing under Testing on the left side of the menu.

  • You can create a closed track by clicking Create track.

  • When creating the closed track, you are given the chance to create a list of testers. Go ahead and create a list and name it.

  • Re-add the email account you used on your test device to the list of test emails and click Save changes.

To make the user a test user, open the registration URL on your test device (or any browser that has logged in as that test user). You can send the URL to your device, for example, by email.

By opening the link in the browser, a web page with the Become Tester button will be displayed. Press the button and your user will be able to make test purchases on your tester.

Adding a Signed Version to the Closed Track

Create a signed APK or use the Android App Bundle to upload a signed APK to the alpha channel you just created. Installing the APK will be enough.

Find more information on this in this support article.

Testing on Android Devices

For testing from a physical device, the following steps are followed:

  • After the Sandbox test account is invited to the application as a tester, the invited email shown below will appear to the logged-in account. Invitation mail content may vary depending on the test environment to be used.

  • After clicking Get started, you will be redirected to the used test environment.

  • In the downloaded application, after triggering the subscribe button on the IAP screen, the native pop-up is shown as the sandbox test account as follows:

Time-based subscription features such as free trials have also been shortened for testing. The following table defines the test times associated with time-based subscription features:

Production subscription period

Test subscription renewal

1 Week

5 Minutes

1 Month

5 Minutes

3 Months

10 Minutes

6 Months

15 Minutes

1 Year

30 Minutes

The account used for the Test is logged in. SettingsAccounts&syncAdd accountGoogle

๐Ÿ”
โžก๏ธ
โžก๏ธ
โžก๏ธ
https://support.google.com/googleplay/android-developer/answer/7159011