Release testing instructions for WC Payments 3.8.0

Changes to express checkouts settings section and second-level pages

Expected outcome

The settings page express checkouts section should display a simple Apple/Google Pay card where the option can be toggled on and off. All other Apple/Google Pay settings should be consolidated into a second-level settings page, accessible via a Customize link.

Testing instructions

• Go to **Payments > Settings` via WP-Admin
• Ensure you see a simple Apple Pay / Google Pay card next to the Express Checkouts section:

• Make sure the Apple Pay / Google Pay checkbox is selected and save settings
• From the front end, add an item to the cart, go to checkout, and attempt to checkout with Apple Pay (safari).
• From the front end, add an item to the cart, go to checkout, and attempt to checkout with Google Pay (chrome).

Second level settings pages

• Back in WooCommerce Payments settings, select the 'Customize' link next to Apple Pay / Google Pay
• Ensure you are directed to the Apple Pay / Google Pay second-level settings page:

• Ensure you can toggle/change the various checkbox and radio fields and saves persist these changes
• Ensure changing these settings impacts the Apple Pay and Google Pay buttons on the front-end

Add Jetpack Sync to support Woo Mobile apps

Expected outcome

Selected options from a remote site are synced to WPcom without having Jetpack-the-plugin.

Testing instructions

For each step asking to verify the result (starting with Expectation), please do:

1. Log in wordpress.com with the account you used to connect your test site.
2. Visit https://developer.wordpress.com/docs/api/console/ and run GET /v1.1/me/sites.

There may be delay in reflecting the correct result but the delay time should not be longer than 5 minutes.

Test case for a new site connecting Jetpack:

1. If your test site has Jetpack-the-plugin active, DEACTIVATE IT.
2. If your test has not connected to Jetpack/WP.com, please do that but no need to go through the KYC process on stripe.com. Otherwise, you can use the site from other tests.
3. In your test site, go to site.com/wp-admin/plugins.php, try deactivating and activating the WooCommerce plugin.
4. Expectation: options.woocommerce_is_active reflects the state of WooCommerce plugin activation. In other words, this value is true if WooCommerce is active, and false otherwise.

Test case for a site upgrading WCPay:

1. MUST-DO: Create a new Jurassic test site.
2. If the test site has Jetpack-the-plugin active, DEACTIVATE IT.
3. Install "WooCommerce Payments" 3.7.x from WP.org in WP Admin > Plugins > Add new > search for "WooCommerce Payments". DO NOT use the testing zip file at this point.
4. Activate "WooCommerce Payments" and connect this site to WPcom. (No need to go through KYC in Stripe).
5. In your test site, go to site.com/wp-admin/plugins.php, try deactivating and activating the WooCommerce plugin.
6. Expectation: options.woocommerce_is_active is always false.
7. Make sure that "WooCommerce Payments" and "WooCommerce" are active.
8. Upload and activate the testing zip file for this week.
9. Expectation: options.woocommerce_is_active is switched to true.