I fixed 30 of 31 failures. Nineteen were left.
A checker that stops at the first problem per item reports a queue depth, not a defect count.
We use Google Analytics to see which pages help people. No ads, no profiles. Privacy Policy
21 posts
A checker that stops at the first problem per item reports a queue depth, not a defect count.
A verification that asserts on the surface you wrote to will agree with you every time.
A command's promises decay silently through ordinary edits. Per-command assertions plus a fixture that removes one guarantee is what makes the decay loud.
An agent reporting success has usually verified the call returned, not the artifact. Reading its own output back is the check it skips most often.
Workers report what they did; nothing reports what nobody did. A pass whose only question is what is missing finds the gaps no individual report can.
A pass-or-fail evaluator forced to rule on insufficient evidence produces a confident guess. A third verdict blocks like a failure while asking for something else.
Discovery of unknown size cannot target a count. Convergence on consecutive empty rounds finds the tail that a fixed number of passes always misses.
Top-N, sampling and no-retry all produce reports shaped like full coverage. A bound that is not named in the output is indistinguishable from completeness.
A gate that has never failed might detect nothing. The red fixture is the only evidence it works — and one that trips on two classes localises neither.
An auto-fix can satisfy a failing check by repairing the code or by weakening the check. Both go green, and only one of them is a repair.
A pipeline that reports green with steps that never ran has two states where it needs three. Not-run must block completion or it silently becomes success.
Staleness checked by timestamp or by memory fails quietly. A digest of the declared inputs, stamped beside the output, makes currency a comparison.