Notes from shipping tested software.
Practical writing on test management, exploratory testing, and what actually changes when small teams move off spreadsheets. No thought-leadership, no vague principle-talk — examples first, opinions clearly labelled.
Exploratory testing that actually gets recorded
Unscripted testing has a reputation for being either pure intuition or pure chaos. It’s neither. Here’s a five-part pattern, six fields per finding, and a worked-example timeline that turns a 60-minute session into a defensible coverage record.
Recent posts
How small QA teams set up test management from scratch (in an afternoon)
A practical step-by-step for a 1–5 person QA team. Real defaults, no implementation consultants, running a real cycle by end of day.
Manual and automation test management — without splitting your release story
Two tools split your release readiness in half. What TestOrchestrator owns today (the manual half), what the public CI ingest API will own next.
Pricing test management without the per-seat tax
Per-seat made sense in 2010. For modern small teams that flex headcount, it punishes the wrong behaviour. The honest case for flat pricing.
5 signs your QA team has outgrown spreadsheets
The tells: nobody trusts which version is current, you can’t answer what was tested last release, onboarding takes a week. What to do about it.