Make a purchase matrix
Select a regular product, a product with options, the last unit and an out-of-stock product. For each, check the price, photo, availability, and cart behavior after changing the quantity. Separately go through the path of a guest and a registered buyer from the phone. This detects errors that are not visible when the administrator views the catalog.
Continue with: OpenCart checkout errors: a diagnostic sequence.
Verify totals and shipping
For different addresses, check the available shipping and payment methods: they may be limited by geographical areas, amount or weight. Compare the amount in the cart, order, payment system and CRM. The repeated callback should not deduct stock again or create another order. Check the coupon even after changing the basket.
Continue with: OpenCart payments: verify callbacks and order status.
Record acceptance evidence
Save the test order number, check time, expected amount and actual status. Make sure that the message is received by the responsible manager and that the link in the email opens the correct site. Before advertising, remove the test goods, restore production settings and repeat the short test without real payment.
Praporonosets & MonJetta: OpenCart and Laravel case study
Is one test order enough?
No. It checks only one combination of product, address, payment and buyer type. The minimum set of scenarios is determined by the actual rules of the store.