A regression test must prove the bug can return
The useful test is not the one that turns green; it is the one that distinguishes the broken behavior from the repaired behavior.
3 min read · Review draft
Reading path / Testing & delivery
Build the evidence before release
Screenshots, tests, measurements and restore rehearsals answer different questions. Use the right artifact for the failure you need to catch.
A suggested sequence
- 01
A regression test must prove the bug can return ↗
The useful test is not the one that turns green; it is the one that distinguishes the broken behavior from the repaired behavior.
- 02
Review generated tests as claims about the product ↗
A large test diff is valuable only when its assertions can reject plausible wrong behavior.
- 03
Accessibility evidence starts where the screenshot stops ↗
A page can look correct and still be unusable by keyboard, screen reader, zoom, or error recovery.
- 04
Ship an artifact you can identify and undo ↗
A release is safer when the reviewed source, built bytes, deployed revision, and rollback target form one traceable chain.
On this shelf
Search the full journal ↗
Freeze the behavior before moving the machinery
Characterization tests give a legacy refactor a visible boundary without pretending every old behavior is desirable.
3 min read · Review draft
Prove the dependency tree you actually changed
An upgrade is a supply-chain change, not a version-number edit.
3 min read · Review draft
Design the API failure before the retry
Clients recover reliably only when errors, side effects, and retry conditions are part of the contract.
3 min read · Review draft
A migration plan is incomplete until restore works
Dry runs reveal lock time and data assumptions; restore rehearsals reveal whether the safety net is real.
3 min read · Review draft
Accessibility evidence starts where the screenshot stops
A page can look correct and still be unusable by keyboard, screen reader, zoom, or error recovery.
3 min read · Review draft
Make the agent measure the same workload twice
A performance patch earns confidence through a stable workload, repeated observations, and an unchanged correctness contract.
3 min read · Review draft
Review generated tests as claims about the product
A large test diff is valuable only when its assertions can reject plausible wrong behavior.
3 min read · Review draft
Ship an artifact you can identify and undo
A release is safer when the reviewed source, built bytes, deployed revision, and rollback target form one traceable chain.
3 min read · Review draft