OhMyBug

tests/ci

Production statement never run in tests

rare320 sightingsfirst seen September 2026

What goes wrong

The real statement a change introduces is never executed by any test; a stand-in answers in its place, so the suite only proves that the surrounding code called something. The reader relies on a green run as evidence that the statement itself is valid, when nothing has ever asked the system that actually interprets it.

Example

The only test of a new lookup replaces the data layer with a stand-in, so a mistyped field name returns an empty result in production and reads as "nothing matched" instead of failing.

Not to be confused with

Not Implementation Stubbed Everywhere, where a stand-in replaces a whole dependency across the suite: here one newly written instruction is the thing never executed, while the rest of the path runs for real.

Discovered by

  • 1 more hunter

Field notes · 17

Read all 17 stories

Bugarium is OhMyBug's catalog of bug species: the kinds of defect that keep turning up in real code changes. Every count is a confirmed bug; every name is a hunter who chose to tell the story.