-
Notifications
You must be signed in to change notification settings - Fork 217
Release testing instructions for the WooCommerce Stripe payment gateway 5.8.0
Diego Curbelo edited this page Nov 8, 2021
·
10 revisions
Note: This test requires that you have the WooCommerce Blocks extension installed on your store.
- Add a product to your cart.
- Go to the page containing the Cart Block.
- Click the Payment Request Button (Apple Pay/Google Pay/Chrome Payment Request).
- Note the list of items and the total.
- Click Cancel to cancel the payment.
- Change the number of items in the cart.
- Click the Payment Request Button again.
- Make sure the list of items and the total have been updated.
Note: This test requires that you have the WooCommerce Blocks extension installed on your store.
- Add a product to your cart.
- Go to the page containing the Cart Block.
- Click the Payment Request Button (Apple Pay/Google Pay/Chrome Payment Request).
- Click Cancel to cancel the payment.
- Click the Payment Request Button again.
- Click Cancel to cancel the payment.
- Change the number of items in the cart.
- Click the Payment Request Button again.
- Click Cancel to cancel the payment.
- Click the Payment Request Button again.
- Click Cancel to cancel the payment.
- Make sure you can interact with the Payment Request Button (i.e. button is clickable, and not greyed out).
- Change the number of items in the cart.
- Again, make sure the Payment Request Button is still active (i.e. button is clickable, and not greyed out).
Note: The tests below require WooCommerce Pre-Orders. Make sure you have it installed and active.
Note: Pre-orders is currently not compatible with the blocks checkout.
Note: For SEPA payments, make sure you follow these steps in order to listen for webhooks, etc.
Note: UPE must be enabled.
- Save
4000000000003220
as a payment method to your account - Add any product to your cart and go to the checkout page
- Checkout with the saved
4000000000003220
card - Fail the 3DS authentication
- Checkout again with the same card
- Complete the 3DS auth successfully
- Go to WooCommerce > Orders
- Make sure the payment was successful (order status should be Processing or Completed).
- Go to your Stripe dashboard
- Note that the payment has a status of Succeeded
- Create a pre-order product with charge upon release:
- a. As a merchant, navigate to Products > Add new.
- b. Set the product title to: "Pre-order product with charge upon release".
- c. Under product data, add a regular price of 10.
- d. Select pre-orders.
- e. Check "Enable pre-orders for this product".
- f. Set an availability time in the future.
- g. Select when to charge: "Upon release".
- h. Click "Publish".
- Paying with "new checkout experience" disabled:
- a. As a merchant, make sure "new checkout experience" is disabled under WooCommerce > Settings > Payments > Stripe.
- b. As a shopper, add the pre-order product to the cart and proceed to checkout.
- c. Pay with a new credit card.
- d. Make sure the order details page has a description at the top saying that you will be automatically charged for your order.
- e. As a merchant, navigate to WooCommerce > Pre-Orders.
- f. Select the recently purchased pre-order, go to Bulk Actions > Complete > Apply.
- g. Make sure the pre-order icon is changed to blue "Completed", and that the related order is "Processing".
- h. Please repeat the steps a-g with a saved credit card, and then with SEPA.
- Paying with "new checkout experience" enabled:
- a. As a merchant, make sure "new checkout experience" is enabled under WooCommerce > Settings > Payments > Stripe.
- b. Repeat steps b-h from step 2.
- Create a pre-order product with charge upfront:
- a. As a merchant, navigate to Products > Add new.
- b. Set the product title to: "Pre-order product with charge upfront".
- c. Under product data, add a regular price of 10.
- d. Select pre-orders.
- e. Check "Enable pre-orders for this product".
- f. Set an availability time in the future.
- g. Select when to charge: "Upfront".
- h. Click "Publish".
- Paying with "new checkout experience" disabled:
- a. As a merchant, make sure "new checkout experience" is disabled under WooCommerce > Settings > Payments > Stripe.
- b. As a shopper, add the pre-order product to the cart and proceed to checkout.
- c. Pay with a new credit card.
- d. Make sure the order details page has a description at the top saying that your order has been received, and no mentions of automatic payments in a future date.
- e. As a merchant, navigate to WooCommerce > Orders and make sure recently created order has a status of "Pre-ordered", and the order amount has already been charged.
- f. As a merchant, navigate to WooCommerce > Pre-Orders.
- g. Select the recently purchased pre-order, go to Bulk Actions > Complete > Apply.
- h. Make sure the pre-order icon is changed to blue "Completed", and that the related order is "Processing".
- i. Please repeat the steps a-h with a saved credit card, and then with SEPA.
- Paying with "new checkout experience" enabled:
- a. As a merchant, make sure "new checkout experience" is enabled under WooCommerce > Settings > Payments > Stripe.
- b. Repeat steps b-i from step 2 also with Bancontact and iDEAL.
Note: The WC Stripe Dev tools is required to
enable/disable
the new Settings user interfase.
- In WC Stripe Dev, enable
UPE redesign
. - Under "Express checkouts" in WooCommerce > Settings > Payments > Stripe.
- a. Enable or Disable express checkouts
- b. Change the
Show express checkouts on
options. - c. Save changes
- In WC Stripe Dev, disable
UPE redesign
. - Under "Express checkouts" in WooCommerce > Settings > Payments > Stripe verify that
Payment Request Buttons
andPayment Request Button Locations
have the options saved in step 2.
- In WC Stripe Dev, enable
UPE redesign
. - Under "Express checkouts" in WooCommerce > Settings > Payments > Stripe click Customize appearance.
- Change the selected option for:
- a.
Call to action
- b.
Appearance
- c.
Theme
- d. Save changes
- In WC Stripe Dev, disable
UPE redesign
. - Under "Express checkouts" in WooCommerce > Settings > Payments > Stripe verify that
Payment Request Button Type
,Payment Request Button Size
andPayment Request Button Theme
match the options saved in step 2.