A guided click check opens a page, clicks an element, waits for the page to settle, and confirms what should have happened. It is the monitor that catches a button which has stopped doing anything.
What it does
- Opens the address you gave it.
- Clicks the element you picked.
- Waits for the page to change or for network activity to stop.
- Checks what should now be true.
The wait matters. A click that triggers navigation and a click that updates the page in place both work, because the check waits for the page to settle rather than assuming a page load.
Why this is the one that matters for a store
A store breaks in a way that page checks cannot see. The product page renders, the price is right, the button is visible, and clicking it does nothing because an app update broke the cart. Every page still returns a normal response.
A guided click check clicks the button and confirms the cart appeared. That is the difference between finding out now and finding out from your sales figures on Thursday.
Good uses
- Click add to cart, confirm the cart appears.
- Click through from the cart, confirm the checkout page opens.
- Click into pricing or booking from the home page, confirm you land where you should.
- Click a primary call to action, confirm the next step renders.
What it will not do
It performs one interaction. It does not chain a long sequence, and it does not sign in, because there is nowhere to store credentials and every check starts from a logged-out browser.
It also cannot complete a purchase. A click check confirms a shopper can reach the checkout page. It does not enter card details and does not place an order.
Setting one up
Choose a click-check template, give it the page to start from, and point it at the element to click. Then choose the assertion: usually that an element now exists, or that the address now matches your checkout path.
Pick a product you know stays in stock. A check pointed at a sold-out item will fail for a reason that has nothing to do with your site being broken.