Absence-Only Check Proves Nothing

What goes wrong

A test protects a rule only by asserting that some text, marker or field is absent ('no error shown', 'log does not contain ERROR'), so a reworded message, a page that never rendered, or an event that never happened all pass exactly like correct behaviour.

Example

The test asserts that no 'Error' text is on the page; the component crashed and rendered nothing, so the test passes.

Not to be confused with

The input is present and the code path runs; not a checker that goes green when its input is missing (Missing Input Green Gate), not a negative case blocked by an earlier refusal (Overdetermined Negative Control), and not a positive text check missing its key word (Text Check Skips The Key Word).

Discovered by

@sks24git GitHub

Field notes · 5

@sks24git2026-11-04

A regression check counted bad writes and passed at zero, but never showed the good write happened at all. If the code under test stops writing that file or moves it, the check stays green and guards nothing.

Pair every "count is zero" check with a positive control. Zero bad events also means zero events.
Assert the path you expect, not only the one you fear.

@sks24git2026-10-30beat 1 review round

A test helper swallows every setup error, and the test checks only that a file was not written. Break setup outright and nothing gets written either, so the test stays green on the exact failure it means to rule out.

Assert the run got past the step, not just what it skipped. A swallowed error also writes nothing.

@sks24git2026-09-13beat 1 review round

A fix threaded one optional argument through three calls, and the test entered at the last one and built that argument by hand. Delete the argument at either earlier hop: it compiles, every test stays green.

Test wiring from the end where it begins. A case that enters at the sink pins the sink, not the path to it.

@sks24git2026-09-10beat 4 review rounds

A scanner asserted only that it had found no offenders, and its pattern could not cross a closing bracket. It reported a clean corpus because it was matching nothing at all.

Assert a scanner saw something before trusting that it saw nothing. Count what it scanned and pin one known hit.
Give every pattern a positive and a negative control.

@sks24git2026-09-05beat 2 review rounds

A "re-sent request is not charged twice" test wrapped the second call in a function and then only counted groups. Refused, replayed and helper-crashed all looked the same, so a balance drain before the dedupe passes.

Never discard the outcome you test. a function around the act turns three different results into one green.
Re-read the money after the replay. No new row is not no charge.