Google Notif Testers of Internal Test Upload Google Console
You should exist testing your integration throughout development. To test during the evolution phase, we recommend leveraging license testers to run through the scenarios described in this topic. To configure license testers, see Test in-app billing with application licensing.
Using license testers provide the post-obit benefits:
- Ordinarily, the Google Play Billing Library is blocked for apps that aren't signed and uploaded to Google Play. License testers can bypass this cheque, significant yous can sideload apps for testing, even for apps using debug builds with debug signatures without the need to upload to the new version of your app. Notation that the parcel name must match that of the app that is configured for Google Play, and the Google account must exist a license tester for the Google Play Console account.
- 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 every bit when a payment is declined. Figure i shows these test forms of payment equally they announced within the purchase period.
- License testers can apace test subscription features.
Hither are some boosted details almost the test purchase process:
- Exam purchases use the same app purchase menstruation used by bodily purchases.
- Taxes are not computed for test purchases.
- Google Play indicates a test purchase by displaying a notice across the center of the purchase dialog.
You can confirm the account that is making a purchase by expanding the purchase dialog. Note the post-obit:
- Test accounts must be on the tester's Android device.
- If the device has more than one account, the purchase is made with the account that downloaded the app.
- If none of the accounts have downloaded the app, the buy is made with the first business relationship.
Earlier distributing your app, you can make utilise of Google Play test tracks to perform additional validation. For instance, you tin can leverage test tracks to have your QA squad qualify a new release.
With examination tracks, users can install your app from Google Play and test a version of your app that is not yet publicly available. Users can make real purchases using any of their payment methods in Google Play.
To test your Google Play Billing Library integration using test tracks, practise the following:
- Publish your app to a exam track. Annotation that after you lot publish an app to a testing track, it tin can have a few hours for the app to be available for testers.
- Ensure each tester opts-in to your app's test. On your test'due south opt-in URL, your testers see an explanation of what it means to exist a tester along with a link to opt-in.
You lot can test your integration on any Android-powered hardware device running Android 1.6 or higher. The about current version of the Google Play awarding must exist installed on the device. For full general information about how to fix upwards a device for use in developing Android applications, meet Using Hardware Devices.
Test one-time products
Test consumable products
When testing consumable products, we recommend testing a variety of situations, including the following:
- A successful buy where the user receives an item. With a license tester, you can use the Exam instrument, always approves payment method.
- A purchase where the payment method failed to be charged, and the user should not receive the detail. With a license tester you tin apply the Test musical instrument, always declines payment method.
- Ensure items can be purchased multiple times.
You should also verify that purchases are properly acknowledged as described in processing purchases. For purchases from license testers, a purchase will be refunded later on three minutes if your app does non acknowledge the purchase and you will receive an email about the cancellation. You tin can as well bank check the Orders tab in the Google Play Console to see if an order was refunded later 3 minutes.
Test non-consumable products
Non-consumables should exist tested the aforementioned as consumables, merely you should verify an item cannot exist purchased again within your app. Be sure to verify purchase acknowledgement for both non-consumables and consumables (when applicable) since the logic to process each the ii types of purchases vary.
Test awaiting purchases
You should test a pending buy where the item should exist granted when the buy state becomes PURCHASED. License testers have access to ii test instruments for delayed forms of payment where the payment automatically completes or cancels later a couple of minutes.
-
Make a purchase with a delayed course of payment "Slow test carte, declines after a few minutes", as shown in Figure 2. Restart the app, validate that the purchase has not been granted.
Effigy two. Test a purchase with a declined slow test card. -
Make a purchase with a delayed class of payment "Slow exam card, approves after a few minutes", as shown in Figure 3. Wait a few minutes, validate that the purchase has been granted.
Figure 3. Test a purchase with an approved wearisome test menu.
You tin can find more than information at Treatment pending transactions.
Exam subscription-specific features
The buy flows for one-time products and subscriptions are similar, but subscriptions have additional scenarios, such as successful or declined subscription renewals. To test renewals, you can use the Exam instrument, always approves and Test instrument, always declines payment methods that are bachelor for license testers, as shown in figure 1. Utilise these payment instruments to exam scenarios across the successful subscription scenario.
Similiar to one-time products, yous should also verify that purchases are properly acknowledged every bit described in processing purchases. For purchases from license testers, a buy will exist refunded subsequently three minutes if your app does not admit the purchase and you lot volition receive an email about the cancellation. You can too check the Orders tab in Google Play Panel to see if an order was refunded afterwards 3 minutes.
Renewal periods
Test subscriptions renew more quickly than actual subscriptions, and test subscriptions can renew a maximum of half dozen times.
The post-obit tabular array lists the testing renewal times for subscriptions of various durations. These times are approximate. You may run across small-scale variations in the precise time of an result. To compensate for variation, phone call the API to view the current status later every subscription expiration appointment.
| Production subscription period | Test subscription renewal |
| i calendar week | 5 minutes |
| 1 month | five minutes |
| iii months | 10 minutes |
| 6 months | xv minutes |
| 1 year | xxx minutes |
Time-based subscription features such equally gratis-trials are as well shortened for testing. The following table identifies the testing fourth dimension periods associated with time-based subscription features:
| Characteristic | Test period |
| Buy acknowledgement | 5 minutes |
| Free trial | iii minutes |
| Introductory price catamenia | Aforementioned every bit subscription test menstruum |
| Grace period (both 3- and 7-day) | 5 minutes |
| Account hold | ten minutes |
| Pause (1 calendar month) | v minutes |
| Interruption (2 months) | 10 minutes |
| Break (3 months) | xv minutes |
Test Cases
Expand the following section by clicking Prove/Hide to evidence testing scenarios you should use to verify your subscription integration.
You tin use the Google Play Panel to create codes for your ain testing. Keep in mind that you may simply create 500 promo codes per quarter across all managed products in an app.
You should examination the post-obit promo lawmaking redemption scenarios:
- When the promo lawmaking is entered in the purchase dialog that was launched within your app.
- When the promo code is redeemed in the Google Play Shop app.
- When the promo code is redeemed at https://play.google.com/store using the Redeem button in the left-mitt navigation.
Inside these scenarios, you should exam redeeming codes in as many means every bit possible. Nosotros recommend perform the following tests at a minimum:
- Redemption before the app is installed.
- Redemption while the app is running in the foreground. Note that for this test, you need another device to test using the Google Play Store app. Exist sure to test redemptions from dissimilar screens in your app.
- Redemption with multi-window way, where both your app and the Google Play Shop app are being displayed at the same time.
For each test, make sure that the item is correctly detected and that the user is notified.
Source: https://developer.android.com/google/play/billing/test
0 Response to "Google Notif Testers of Internal Test Upload Google Console"
Post a Comment