Too much of a good thing: the trade-off we make with tests

from blog ntietz.com blog - technically a blog, | ↗ original
↗ original
I've worked places where we aspired to (but did not reach) 100% code coverage. We used tools like a code coverage ratchet to ensure that the test coverage always went up and never down. This had a few effects. One of them was the intended effect: we wrote more tests. Another was unintended: we would sometimes write unrelated tests or hack things...