Getting started on day one
- 1Pick your three key flows
What would lose you customers if it broke? Sign-up, ordering, booking or the contact form.
- 2Prepare a test account
A username and password used only for testing, with fake data so it never mixes with real customer orders.
- 3Give it the address and the goal
State the expected result clearly: 'after payment a confirmation page shows the order number'.
- 4Review the test cases
Remove what does not matter, add what only the business owner knows, then run.
- 5Sort bugs by severity
Fix whatever blocks a sale first and leave cosmetic notes for later.
- 6Re-test and schedule
Run again after the fix, then set it to run regularly.
What to ask before choosing a tool
- Can it test a site that was not built on their platform?
- Can I see and edit the test cases before they run?
- Does the report include screenshots and steps to reproduce?
- Does it re-test after a fix and run on a schedule?
- What does it not test? An honest answer is a good sign.
Who reads the report?
Name one person who reads the report after each run and decides what gets fixed. The agent finds and documents the bug; the decision stays yours. If you have a developer, forward the bug report as it is, since it is already written in the form they need.