Select a product and check that it appears in your cart with the correct variant and quantity. Repeat the test on mobile and after significant theme or app changes.
An Add to Cart button can look normal but fail when clicked. A theme change, script error or conflicting app may stop it from working, or it may add the wrong item or quantity.
Open a product page, select any required options and click Add to Cart. Confirm that the cart updates with the expected product, variant and quantity. Repeat the check for important products and on mobile, especially after a change.
How to set this up in Acumen Logs
In your project, select Create New Synthetic Test, give it a name and enter the product page as the Startup Page URL.
Choose the emulated device you want to test. Build the journey manually or use the Chrome recorder to capture the product selection and Add to Cart steps.
Add a check for the expected cart element or text, such as the product name. Save the journey and test.
Use Run to test it, then inspect the result and screenshots. Configure alerts and, if your plan supports it, enable a schedule.
Set up a synthetic test and build the add-to-cart journey.
The AI journey generator includes e-commerce templates, including Add to Cart. The selected example shows a checkout flow; use safe test data and a sandbox where appropriate.
Test each important product or variation separately as needed: a passing journey only covers the steps and data it actually exercises. Read the synthetic setup guide.
What debugging evidence is captured when a monitor fails?
Synthetic runs capture step-by-step screenshots, JavaScript console errors, and network logs on all plans, plus video replay and trace logs on Essentials and Pro.
What happens to synthetic tests when our website layout changes?
Elements are recognised by what they are for—such as a "Submit order" button—rather than just a CSS class name, so routine markup changes do not break the journey.
How do I monitor login flows and authenticated SaaS dashboards?
Build a synthetic browser journey that signs in using encrypted credentials stored in Secrets, then verifies that key dashboard components load without console errors.
Will synthetic checkout tests create fake orders in my store?
Not if the journey is configured appropriately. Use a staging store and payment sandbox, or stop before submission; check for order and inventory side effects.