A plugin can activate successfully and still behave unexpectedly with your theme, payment setup or other extensions. Test the shopping tasks it touches before relying on it during a campaign.
Write down the change you expect
Start with one sentence: “Shoppers should see the amount remaining for free shipping,” or “Customers should be able to edit quantities in the side cart.” This gives your test a clear purpose. Add the plugin version, WordPress and WooCommerce versions, active theme and date to your notes.
Use a staging copy where possible and keep a restorable backup. Change one feature at a time so that an unexpected result is easier to trace.
Check the product page before adding anything
Open a product that should use the feature and one that should not. Verify the price, variation selection if relevant, stock message and add-to-cart button. Make sure demonstration content, sample phone numbers or promotional messages have not appeared across the live store.
Test the basket as a sequence
- Add one item.
- Add another qualifying item.
- Change a quantity.
- Remove an item.
- Apply and remove a coupon.
- Empty the basket and start again.
Watch totals and messages at every step. A shipping progress bar, a cross-sell and a quantity discount may all react to the same change. Their combined result matters more than each feature working alone.
Use your actual cart and checkout type
Confirm whether your pages use WooCommerce blocks or the classic experience. WooCommerce documents the Cart and Checkout layouts separately, and extension behaviour should be checked against the pages your store actually uses.
If you are evaluating Checkly’s checkout options, start with its live demo, then verify your own required fields, validation messages and payment options. A demo cannot reproduce every store configuration.
Repeat as a guest on a phone
Use a signed-out session for the customer test. Your administrator account can bypass notices or prefill fields that a new visitor still has to complete. Check the menu, overlays, close buttons and checkout link on a narrow screen. Try the flow with the keyboard open and after rotating the phone.
Separate an interface check from a payment test
Seeing a payment field is not proof that an order can be paid. For an end-to-end payment test, use your provider’s supported test environment and verify the order status and confirmation. Avoid switching a live shop into test mode while real customers are purchasing.
For downloadable products, also check the customer’s email, account access and download link using the authorised test purchase. For physical goods, review the shipping method and delivery details saved with the order.
Keep a small result log
Record each test as passed, failed or not tested. Include a screenshot and reproduction steps for a failure. “Checkout opens” and “payment completed” should be separate lines. After a fix, repeat the failed step and the steps immediately around it.
Frequently asked questions
Do I need to test unrelated features?
Focus on the pages and interactions the plugin touches, then run one complete purchase journey to catch effects elsewhere.
What should I do if something breaks?
Pause the new feature, preserve the details of the failure and use your staging site to isolate the interaction. Share the steps and versions with support.