Tutorials·13 June 2026 · 7 min read
How to write test cases developers actually read
Test cases that get read are short, scannable, and written for the person who has to act on them. Here is the format I use.
manual-qatest-casesdocumentation
Tutorials·13 June 2026 · 7 min read
How to report bugs developers can fix quickly
A bug report exists to get the bug fixed. Specific title, minimal repro steps, explicit expected-vs-actual, evidence, and environment — the format that prevents "can't reproduce".
manual-qabug-reportsdocumentation
Tutorials·13 June 2026 · 6 min read
What good QA handover notes look like
Write an operating manual for the arriver, not a diary: current state, setup, known issues with status, gotchas, and pointers — so someone can take over without asking you.
test-managementdocumentationhandovertemplate
Opinions·27 November 2025 · 8 min read
Test plans nobody reads, and the one-page replacement that works
The 40-page IEEE 829 test plan: written once at kickoff, opened twice during the project, abandoned after release. There's a single-page replacement that teams actually update.
processdocumentationtest-plansculture
Opinions·25 November 2025 · 8 min read
API tests as documentation — and why that's the only test suite anyone reads
Wiki pages about APIs go stale in three months. The API test suite gets opened every single day. Write tests that read like documentation — and stop writing the wiki.
api-testingdocumentationpatterns