How checkout monitoring works

The flow

Every run walks one path: open a product page, add to cart, open the cart, start checkout, enter a shipping address, choose a shipping method, reach the payment step, and — where enabled — place the order. The browser is a real Chromium instance, so client-side JavaScript, third-party widgets, consent banners and promo popups all execute exactly as they do for a customer.

MageSentinel resolves the selectors for each step across Luma, Hyvä Checkout and one-step checkout without any theme-specific configuration. You give it a store URL and a product; it finds the rest.

What each step asserts

Reaching the next page is not enough. At the cart, MageSentinel checks the SKU, quantity and line price against what the product page showed. At checkout it checks the order summary — subtotal, shipping, tax, grand total — arithmetic included. If real order placement is enabled for the plan and store, it confirms the order was created and reads back its number and total.

A run only passes when every assertion on the path passes. A store that loads perfectly but quotes the wrong price is a failed run, not a passed one.

No install required

The core product works against your storefront from the outside, with nothing added to the store. An optional read-only Magento connector module adds deeper root-cause data — store version and mode, third-party modules, cron health, queue depth, recent logs — but the monitoring itself never depends on it.