Test Notes
Test design, kindly explained.
Practical notes on designing tests, testing before release and writing bug reports people can act on. Written by Malwina, a senior QA engineer with ten years of testing behind her.
No tester on the team? A 30-minute smoke test before every client handover
Small agencies rarely have a tester. A short, repeatable smoke test before each handover catches the embarrassing bugs, and it takes about half an hour.
Read the articleBoundary value analysis, explained with a signup form
Bugs cluster at the edges. Boundary value analysis tells you exactly which values to test, so a handful of test cases covers what a hundred random ones would miss.
ReadThe pre-launch testing checklist I use on every website
Before a website goes live, I test six areas in a fixed order: journeys, forms and emails, devices, content, the basics of accessibility and what happens when things go wrong.
ReadHow to write a bug report developers can fix in minutes
A good bug report answers five questions before anyone has to ask them. Here’s the structure I’ve used for ten years, with a template you can copy.
Read
A testing question worth a note?
Send it over. If it’s useful to others, it may become the next Test Note, and you’ll get a straight answer either way.
Ask a question