Release testing instructions for WC Payments 9.1.0 - Automattic/woocommerce-payments GitHub Wiki
fix: Manual capture fails in the transaction detail screen with a customized order number
PR https://github.com/Automattic/woocommerce-payments/pull/10435
- Install and activate a sequential order number plugin (like Sequential Order Numbers for WooCommerce or Sequential Order Numbers Pro for WooCommerce, which can be downloaded from here by any Automattic staff)
- Create a new order with a payment that requires manual capture
- Try to capture the payment from the transaction detail screen
- Verify that the capture succeeds and no errors occur
- Verify that order and subscription numbers are displayed correctly in the transactions list
Fix: Update Safe Mode notice to be consistent with new changes from Jetpack #10511
PR https://github.com/Automattic/woocommerce-payments/pull/10511
- Install this plugin https://jetpack.com/download-jetpack-beta/, then activate
jetpack-debug-helper
, thenIdentity Crisis Simulation Utility
. - Trigger between two types of notices, use this constant in wp-config.php, and change its value to either
development
orproduction
:define( 'WP_ENVIRONMENT_TYPE', 'development' );
- Expect: see two different notices.
- Expect: in the two notices, all text contents and links are WooPayments-relevant.
Fix: Using 3DS cards for changing payment method for subscription use-case
PR: https://github.com/Automattic/woocommerce-payments/pull/10453 (feel free to ping @timur on Slack if any questions)
- Purchase a subscription with a normal non-3DS card
- Navigate to change payment method flow and change payment method to a 3DS
4000002760003184
with the following use-cases- Upon authorization, cancel the modal window from the top right side and confirm
- The
We are unable to authenticate your payment method. Please choose a different payment method and try again
error on the page - Subscription has the old payment method still attached
- The
- Click on "Change payment method" once again, this time fail the authorization and confirm that
We are unable to authenticate your payment method. Please choose a different payment method and try again.
notice is visible- Subscription has the old payment method still attached
- Uncheck the
Use this payment method for all of my current subscriptions
checkbox and confirm the authorization- Once the confirmation modal pops up, confirm there is no success notice displayed behind the pop-up window since we're still in the process of confirming the payment for 3DS
- Confirm that you are redirected to the subscription details page under my account
- Confirm tha the successful
Payment method updated.
notice is displayed
- Check the
Use this payment method for all of my current subscriptions
checkbox and confirm the authorization- Confirm that you are redirected to the subscription details page under my account
- Confirm that the successful
Payment method updated for all your current subscriptions.
notice is displayed - Confirm that all the subscriptions were updated with the new payment method
- Upon authorization, cancel the modal window from the top right side and confirm
- Change payment method to a new non-3DS card
- Change payment method to a saved card (both 3DS and non-3DS)
- Use the insufficient funds 3DS card
4000000000009995
and confirm the card is not attached to the subscription after failure, and the correct error notice for insufficient funds is being displayed - Process renewal for a subscription that has a 3DS card attached to it as a result of a change payment method flow
- Upon renewal processing attempt, the order should be expectedly put
On hold
and once you navigate to the link in the renewal order email sent to the shopper, you should be able to successfully renew order with a 3DS card - Perform the same test, but change to a non-3DS card during renewal order
- Upon renewal processing attempt, the order should be expectedly put
Fix: WooPayments gateways are always ordered as a group on the checkout page
PR: https://github.com/Automattic/woocommerce-payments/pull/10485 (feel free to ping @timur on Slack if any questions)
- WooPayments at the beginning
- Set WooPayments as the first payment method under WooCommerce Core > Settings > Payments
- Enable other payment gateways such as Cash on delivery etc.
- Refresh the settings page:
- Reload the WooCommerce payments settings page.
- Verify that WooPayments is positioned as the first gateway in the list.
- Go to the checkout page (via shortcode or blocks) and confirm that WooPayments is displayed as the first payment option.
- Activate LPMs and/or APMs within WooPayments.
- Ensure that the LPMs/APMs appear immediately after the main card gateway and before any other gateways.
WooPayments is in the middle
- Set WooPayments in between other gateways in WooCommerce Core payments settings
- Navigate to the shortcode/blocks checkout and confirm WooPayments gateways are placed between other plugins
WooPayments at the end
- Set WooPayments at the end of order in WooCommerce Core payments settings
- Navigate to the shortcode/blocks checkout and confirm WooPayments gateways are placed after other plugins