Test coverage quickly hits diminishing returns. The question thus becomes "what is the optimal coverage for this use case"? But that's not an easy question to automate answers to, so we often fall back to it's cousin "what % of LOC do we cover", and then assume more is better.
-
-
-
In reality, that can result in make-work which diverts from actual code improvement. Therefore, many developers shy away from it entirely, because it's easier to resist from zero than from halfway. Meanwhile, overtesting remains an acceptable mode of failure for a clock-puncher.
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.