~100% unit test code coverage discourages defensive programming.
1) guards. if f=x: raise
2) early returns. if f=x: return.
3) except block. Can't trigger an error? remove the catch!
1)&2) may or may not be a common case, but there might be many, many of these in a code base.
But high code coverage isn't bad. It's just that 80-90% is as far as you can get before you need tail wag the dog tricks to get coverage on the last uncovered lines.
♡ 0 ↻ 0