What should I test after updating my website, theme or apps?

A small update can affect an unrelated part of a website. A theme change might alter a product page, an app may conflict with another script, or a form update might prevent an enquiry from being submitted.

After a change, check key landing pages and navigation, then test important forms and login flows. For a store, select a product, add it to the cart and check the checkout journey. Repeat important steps on mobile. Use staging and test data when possible; check for unintended orders, charges and notifications if testing a live store.

How to set this up in Acumen Logs

1. In your project, select Create New Synthetic Test, name the test and enter the relevant starting page URL.
2. Choose an emulated device, then record or build the key actions and checks for that journey. For example, open a product, select a variant, add it to the cart and verify the cart.
3. Save the journey and test. After an update, use Run on the Synthetic Test Dashboard to execute it on demand.
4. Review screenshots, console errors and network requests when a step fails. Update the journey if a legitimate change alters the flow.
5. Where your plan supports scheduling, enable a schedule and configure alerts for the journey.

For checkout tests, use a staging store and payment sandbox when testing through confirmation, or stop before live submission and verify any side effects. Read about safe checkout tests.