Release testing instructions for WC Payments 5.7.0

Test Fraud and Risk tools

1. Create site

Create a new site, complete the setup wizard, and select USD as the store currency and LA, USA as the store address.

2. Enable the fraud protection feature by running the following WP CLI command:

wp option update wcpay_fraud_protection_settings_active 1

3. Discoverability banner view

1. Important: To make testing this banner as easy as possible, please login to your site from a separate private (or incognito) browser window.
2. Navigate to the WCPay Overview page: /wp-admin/admin.php?page=wc-admin&path=%2Fpayments%2Foverview.
3. Inspect the banner. It should look like this:

4. Click the 'Learn more' button. You should be directed to the WCPay settings screen. Once the components finish loading, you should see the screen smoothly scroll down to the Fraud Protection section.
5. Go back to the WCPay Overview page: /wp-admin/admin.php?page=wc-admin&path=%2Fpayments%2Foverview.
6. Click 'Remind me later'. The banner should disappear.
7. Now click the Deposits link just below the Overview link in the left sidebar. Once the Deposits screen loads, click back to the Overview screen. The banner should not appear.
8. The 'Remind me later' button will set a timestamp for three days in the future. The banner will not appear until that timestamp is in the past.
9. Now log out and close your private browser window.
10. To speed up testing, update the option that controls the banner behavior to set the remindMeAt timestamp to null. If you get the option from the database, via WP CLI, after clicking the 'Remind me later' button once, the option will look something like this:

wp option get wcpay_frt_discover_banner_settings

{"remindMeCount":1,"remindMeAt":1679751133141,"dontShowAgain":false}

11. Copy and paste the returned option into a text file, then update the option to set remindMeAt to null, leave remindMeCount and dontShowAgain at their current values. Paste your updated option string at the end of the WP CLI option update command. Make sure the option value is wrapped in single quotes like the example below.

wp option update wcpay_frt_discover_banner_settings '{"remindMeCount":1,"remindMeAt":null,"dontShowAgain":false}'

Success: Updated 'wcpay_frt_discover_banner_settings' option.

12. Open a new private browser window, login to your site, and visit the overview page again. The banner should show up.
13. Repeat steps 6 through 12 two more times.
14. At this point you should have clicked the 'Remind me later' button three times. The remindMeCount value in the option should now be 3 and the remindMeAt value should be null after your final update of the option in step 11. The option should look like this:

wp option get wcpay_frt_discover_banner_settings 

{"remindMeCount":3,"remindMeAt":null,"dontShowAgain":false}

15. Open a new private browser window, login to your site, and visit the overview page again. The banner should appear, but this time it should include a 'Don't show me this again' button. The banner should look like this:

16. Click the 'Don't show me this again' button. The banner should disappear. Now click around to different admin screens and the Overview screen periodically for the next minute. You should not see the banner render on the Overview screen any more.

4. Fraud tools welcome tour

1. Go to Payments > Settings
2. The welcome tour should pop up
3. Go through the tour steps and finish it – or click on the close button
4. Refresh the page – it shouldn't pop up again
5. Check the welcome tour flag by running wp option get wcpay_fraud_protection_welcome_tour_dismissed – it should return 1
6. If you want to test it again, run the following command: wp option update wcpay_fraud_protection_welcome_tour_dismissed 0

5. Main feature setting panel

1. Login into the admin of your site and visit the WCPay settings screen: /wp-admin/admin.php?page=wc-settings&tab=checkout&section=woocommerce_payments
2. The fraud protection section should now be rendered below the deposits section.
3. Click the question mark icon beside each option under the payment risk level to ensure that the correct modal displays.
4. Ensure that modals close when clicking 'Got it' button, 'X' close button, and clicking outside of the modal.

Currency changes are reflected

1. Navigate to the WooCommerce general settings page and change your currency to a currency other than USD.
2. Navigate back to the WCPay settings page and open each fraud protection modal by clicking on the question mark symbol '?'. The rule referencing $1,000.00 should now show a slightly modified text mentioning the equivalent of $1,000.00 in $store_currency.

6. Advanced section

1. Go to WCPay Settings, and you should see the "Fraud Protection" section at the bottom of the page (before the "Advanced settings" link).
2. Check the "Advanced" protection level and click on "Configure".
3. You should be redirected to the "Advanced fraud protection" page.
4. Scroll to the "Purchase Price Threshold" rule and check "Screen transactions for abnormal purchase prices".
   1. Check also the "Block Payment" input on the same box
5. Change the "Maximum purchase price" input to be 150.
6. Scroll down to the "Order Items Threshold" rule and check "Screen transactions for abnormal item counts".
7. Change the "Minimum items per order" input to be 3.
8. Also change the "Maximum items per order" input to be 5.
9. Open your shop in incognito mode, add 2 items to the cart, and do the checkout.
   1. The order should be received.
10. Go to the shop again, add 6 items to the cart, and do the checkout.
    1. The order should be received.
11. Close the previous browser window and open a new one – also in incognito mode. Add products until the total cart price surpasses the equivalent of US$ 150, and do the checkout.
    1. An error message should appear.

7. New tabs on the transactions page

1. Go to Payments > Transactions.
2. You should see "Risk review", and "Blocked" tabs.
3. Click on "Risk review" and click on the first item of the table.
4. You should be redirected to the payment details page.
5. Check if the status is "Needs review" and two buttons are visible at the top of the page "Block transaction" and "Approve transaction"

6. The timeline (in the middle) should contain the reason why it was put on review

7. Click on "Block transaction"
   1. The button should be in a loading state while the "Approve transaction" button should be disabled
8. After finishing the request, the data will be fetched again
   1. The status should be "Payment blocked"
   2. There should be a timeline entry with "Payment was blocked by <your_user>"
   3. Refresh the page and confirm that the data stills the same
9. Open the transactions page again – select the "Risk review" tab and click on the first item
10. Click on "Approve transaction"
    1. The status should be "Paid"
    2. There should be a timeline entry with "Payment was approved by <your_user>"
    3. Refresh the page and confirm that the data stills the same
11. Open the transactions page again – click on the "Blocked" tab and click on the first item
    1. The status should be "Payment blocked"
    2. The timeline should contain "Payment was screened by your fraud filters and blocked." alongside the list of rules that were triggered.
    3. Refresh the page and confirm that the data stills the same

Test Cancel Confirmation Modal

1. Test Cancel Confirmation Modal

2. Place an order.

3. On the admin dashboard 'Edit Order' screen, select "Cancelled" from the Order Status dropdown

4. A confirmation modal should be displayed with the option to "Do Nothing" or "Cancel Order", which warns the merchant that Cancel order will not refund the customer.

5. On click of Do Nothing, the order status dropdown is reset back to its previous status, on click of Cancel Order, it is retained as Cancelled.

6. If the order does not have any amount to be refunded (not successfully placed/ already refunded), the modal should not be displayed.

7. Regression testing of Refund Confirmation Modal

• When user clicks on Refund, the refund Confirmation Modal should be displayed as before and user can Cancel or choose to Refund the order before changing status to Refund
• If the order is already refunded, show an error. (styling of error message is changed)