The itch every test writer knows
Most static analysis setups enforce a rule like "keep Cyclomatic Complexity (CC) under 10." It's a well-known heuristic from the 1970s, and it works reasonably well as a rough tripwire.
But if you've ever tried to hit 100% branch coverage on a function the linter rated "CC: 6, safe," you've probably felt this:
"The tool says this is fine. Why does writing exhaustive tests for it feel like solving a puzzle?"
That gap is real, and it comes from two blind spots baked into how CC counts branches.
