-
Notifications
You must be signed in to change notification settings - Fork 69
Release testing instructions for WC Payments 3.6.0
jessy edited this page Jan 11, 2022
·
15 revisions
- It would be best to run these tests last as it requires having completed transactions on the connected account.
When the total number of WCPay transactions is less than or equal to the number of visible transactions in the transactions list, an export will immediately be downloaded. Otherwise, if the transactions list is filtered, OR the total number of transactions exceeds the number of visible transactions in the transactions list, an async export will be emailed to the merchant.
- Ensure there are between 1 and 100 WCPay transactions completed on the connected account
- Via WP-Admin go to Payments > Transactions
- Expand the number of rows in the list to 100, then click the download button
- Ensure a CSV containing the transactions listed in the table view immediately downloads
- Access the following JN test site: https://civilian-partridge.jurassic.ninja/wp-admin (login details will be provided by release lead)
- Via WP-Admin go to Payments > Transactions
- Expand the number of rows in the list to 100, then click the download button
- Ensure a notification appears indicating an export will be emailed to the email address associated with the WCPay connected account.
As there are currently no test accounts containing > 10000 transactions, it's not possible to test this case.
- This issue is ideal for exploratory testing to ensure there are no other scenarios for GPay saved cards which cause user to not be able to checkout.
Able to checkout using Google Pay.
- Log into https://pay.google.com/
- Make sure the card saved is missing the billing address name which is optional in Google Pay but mandatory in WooCommerce
- Attempt to purchase a product via the branded "G Pay" button.