A one-day test plan
- 1List the flows
Everything a visitor does: browse, sign up, order, pay, get in touch. Five to ten flows are enough.
- 2Run each flow to the end
From the first page to the confirmation message and the email or text that follows it.
- 3Break things on purpose
Leave a field empty, type a short phone number, press the button twice, go back in the middle of payment.
- 4Open it on a phone
Most visitors are on phones. Check that nothing runs off the screen and buttons are easy to tap.
- 5Re-test after every fix
Fixing one bug can break something else, so repeat all the core flows.
What to check in each part
| Part | What to confirm |
|---|---|
| Forms | A clear error message in the page's language, and nothing the customer typed is lost |
| Payment | One successful and one declined test transaction, and a correct confirmation page |
| Language | Arabic reads right to left, English is complete with no leftover text |
| Links | No broken link and no empty page, especially in the footer |
| Speed | The first page opens acceptably fast on mobile data |
Do I need a tool?
For a small site, manual testing from a written list is enough. But repeating the same list after every change is tedious and gets dropped over time, which is where a testing agent helps by repeating it for you. There is a ready list in the website testing checklist.