Search for a command to run...
Completing a test run locks it — 409, no edits of any kind. But the lock has deliberate holes: notes, evidence and defects stay open, because triaging a red run is exactly what those are for.
Most defects are filed from a blank form and lose the run that produced them. Raising one from a step carries the reproduction path, the resolved data and the expected result — and records which step it came from.
Store a test run as a list of pointers and the steps drift while the verdict stays put. Hawzu copies the test case into the run and pins its versions — which is what makes execution history mean anything.
Most QA dashboards are built in week one and abandoned by month three. A guide to designing around decisions rather than available fields, the charts worth having, and the ones that quietly mislead.
Most QA reports are written for nobody in particular and get skimmed once. A guide to choosing the report for the audience, the four numbers worth leading with, and why a report that recalculates isn't a record.
Spreadsheets are a reasonable place to start managing test cases. This is what they're genuinely good at, the four things that break as a team grows, and how to migrate without losing what you've built.
A practical guide to managing user acceptance testing — scoping the cycle, giving business testers access without handing them a QA tool, tracking progress, and producing a sign-off artefact that still means something later.
A guide to designing a defect workflow that survives contact with a real team — how many states you need, why priority and severity are different fields, and what breaks when bugs live in two systems.
A completion percentage says nothing about what's left, who holds it, or whether the date is still real. A guide to the statuses that carry information, why mid-cycle pass rate misleads, and what to track instead.
