diff --git a/docs/html/google/play/billing/billing_testing.jd b/docs/html/google/play/billing/billing_testing.jd index b277c4f101fcb..0c64ee4af1b75 100644 --- a/docs/html/google/play/billing/billing_testing.jd +++ b/docs/html/google/play/billing/billing_testing.jd @@ -26,16 +26,27 @@ implementation:

-

To test In-app Billing in an application you must install the application on an Android-powered -device. You cannot use the Android emulator to test In-app Billing. The device you use for testing -must run a standard version of the Android 1.6 or later platform (API level 4 or higher), and have -the most current version of the Google Play application installed. If a device is not running the -most current Google Play application, your application won't be able to send In-app Billing -requests to Google Play. For general information about how to set up a device for use in +

To test in-app billing, you need to publish your app to an alpha +or beta channel in Google Play.

+ +

After you publish an app to an alpha or beta channel, it can take a few hours +for the app to be available for testers. The version code of an APK on a test device +must match the version currently uploaded to the alpha or beta channel on Google Play.

+ +

Important: To test in-app products or make in-app +purchases in your alpha or beta channel app, each tester +needs to opt-in +to your app’s alpha or beta test. On your test’s opt-in URL, your +testers will get an explanation of what it means to be a tester and a link to opt-in.

+ +

You can test on any Android-powered hardware device running Android 1.6 or higher. +The most current version of the Google Play application must be installed on the device. +For general information about how to set up a device for use in developing Android applications, see Using Hardware Devices.

@@ -45,16 +56,21 @@ Devices.

-

The sections below provide more detail about how to use these approaches for +

In either case, you need to publish your app to Google Play's +alpha + and beta release channels to manage the users who can make purchases.

+ +

The sections below provide more detail about how to use these approaches for testing and validation.

+ +

Test Purchases (In-app Billing Sandbox)

Test purchases offer a secure, convenient way to enable larger-scale testing @@ -98,8 +114,14 @@ href="#billing-testing-test">Setting Up for Test Purchases.

within 15 minutes those users can begin making test purchases of your in-app products.

-

Note: To make test purchases, the license test -account must be on the user’s Android device. If the device has more than one +

Important: After you publish your app +to an alpha or beta channel, your testers need to opt-in +to your app’s alpha or beta test using the provided opt-in URL before they +can make test purchases.

+ +

Note: License test accounts +must be on the user’s Android device. If the device has more than one account, the purchase will be made with the account that downloaded the app. If none of the accounts has downloaded the app, the purchase is made with the first account. Users can confirm the account that is making a purchase by expanding the @@ -168,6 +190,12 @@ payment methods in Google Play to make purchases. Note that if you include test license accounts in your alpha and beta distribution groups, those users will only be able to make test purchases.

+

Important: After you publish your app +to an alpha or beta channel, your testers need to opt-in +to your app’s alpha or beta test using the provided opt-in URL before they +can make test purchases.

+

Testing with Static Responses