The people building Hawzu
Notes from the team building Hawzu — how it works inside, and what we have learned about running QA well.
The prompt said scenarios must be distinct. It said so the entire time the model was returning five overlapping ones. And the control we shipped for multi-step cases turned out never to reach the model at all.
Team Hawzu · Aug 26, 2026 · 8 min Ask most QA assistants whether a release is ready and you get the general opinion of the internet. The useful answer depends on what your team wrote down — which means the retrieval matters more than the model.
Team Hawzu · Aug 19, 2026 · 5 min Observatory's insights carry their question as a first-class field, and the scorecard reports how much of your automation your builds have actually run — not how much your test cases claim.
Team Hawzu · Aug 5, 2026 · 4 min You open a release you signed off in March. The numbers are different now. Nothing was tampered with — the world simply kept moving, and the report kept recalculating.
Team Hawzu · Jul 8, 2026 · 5 min Drawing a line between a requirement and a test case is the easy part. Traceability is what happens to that line six months later, when the requirement has children and the defect no longer points at a step.
Team Hawzu · Jun 3, 2026 · 6 min Every team builds a QA dashboard in the first month and stops opening it by the third. The charts aren't wrong — nobody ever decided what any of them was supposed to change.
Team Hawzu · May 20, 2026 · 8 min A QA report that tries to serve the whole company serves nobody. The useful question isn't what to include — it's who is reading, what they'll do next, and whether the number will still say the same thing next month.
Team Hawzu · May 6, 2026 · 10 min Almost every QA team starts in a spreadsheet, and most stay longer than they meant to. The interesting question isn't whether Excel is 'wrong' — it's which specific thing breaks first, and what you lose on the way out.
Team Hawzu · Apr 15, 2026 · 10 min UAT has different testers, a different goal and a different output than QA testing. You rarely need a dedicated UAT feature to run it well — you need to know which ordinary parts to assemble, and where the fit genuinely stops.
Team Hawzu · Mar 25, 2026 · 11 min Most defect workflows fail in one of two directions: too many states nobody maintains, or too few to answer 'who has this now?'. The interesting decisions are about ownership and handover, not the diagram.
Team Hawzu · Mar 4, 2026 · 10 min "We're 80% executed" is the number everyone reports and almost nobody can act on. Tracking a cycle well means knowing what's left, who holds it, and which results aren't finished being results.
Team Hawzu · Feb 11, 2026 · 9 min Someone deletes forty obsolete test cases on a Friday. The interesting question isn't whether they're gone — it's what happened to every run that ever exercised them.
Team Hawzu · Jan 8, 2026 · 5 min Someone improves the login sequence. Three hundred test cases use it and forty runs are in flight. Reuse is the easy half; the version is the half that makes reuse safe.
Team Hawzu · Dec 4, 2025 · 5 min Test documentation isn't written for the person who wrote it. It's written for whoever runs it in eight months — and almost every decision about detail, structure and reuse follows from taking that seriously.
Team Hawzu · Nov 12, 2025 · 11 min Every regression suite grows and almost none of them shrink. The management problem isn't writing the tests — it's deciding what belongs, what runs this cycle, and what to do about the ones nobody trusts.
Team Hawzu · Oct 15, 2025 · 12 min A tester should be able to run tests without being able to reshape the run. That sentence is trivial to say and impossible to express as view, create, edit or delete.
Team Hawzu · Sep 17, 2025 · 5 min One status field usually ends up doing two jobs: recording what a human decided, and implying what the data found. Those need to be different fields, and only one of them should be typeable.
Team Hawzu · Sep 3, 2025 · 5 min You reopen last month's run to fix one result and the server refuses. That refusal is the feature — but what it refuses, and what it deliberately still allows, took more thought than the lock itself.
Team Hawzu · Aug 6, 2025 · 5 min "Checkout is broken." Every QA team has filed that defect and every developer has bounced it. The information wasn't missing — it was on screen, and the form didn't ask for it.
Team Hawzu · Jul 8, 2025 · 5 min Someone edits a test case. What happens to the run that used it last week? The answer decides whether your execution history is evidence or decoration.
Team Hawzu · Jun 4, 2025 · 5 min 
