+ One running example: parsing an availability, meaning a date and + weekly hours. The date 2026-02-30 must be rejected, 2028-02-29 must be + accepted, and 168 hours is the upper boundary of a week. +
++ {line} +
+ ))} ++ + Download the sample report (sample-delivery-report.md) + +
++ AI-built code often arrives with few tests, or with tests that only + repeat the implementation. I do not start by rewriting. I write the + expected behavior as cases for the parts that matter most, run them + against the existing code, and let the failures show what is really + broken. Then I add a mutation baseline so you can see which tests + would not notice a bug. +
++ Coverage tells you which lines ran during the tests. It does not tell + you whether the tests would notice a bug in those lines. Mutation + testing changes the code on purpose and checks that a test fails. That + is the question you care about. Coverage stays useful as a gap finder: + it points at code nothing exercises. It is not a goal, and a high + number alone proves little. +
++ Two systems where I run this: a Rust and Solidity liquidation system + across 7 chains, with a zero-survivor mutation gate and a coverage + ratchet, and the domain core of this website, which has its own tests + and mutation gate. +
++ {item.text} +
++ A 20-minute intro call is enough to see whether this fits your team. +
++ Step {index + 1} +
+{step.rule}
++ {line} +
+ ))} +