Post

Alan Ridlehoover
@alan.codegardener.com

Have you ever been told by an executive that test coverage past 80% produces diminishing returns? Have you asked them which 20% you should not test? Have they ever given you an answer?

1 repost7 likes

Lucian Ghinda
@lucianghinda.com

I so strongly agree. This idea of having a number as the best test coverage while also only checking line coverage is a very bad metric :) It often create confidence instead of being careful

Alan Ridlehoover
@alan.codegardener.com

Totally! False confidence. Bugs can still sneak in with 100% line & branch coverage. But, without 100% coverage, you cannot refactor code with full confidence. It's not about bugs. It's about moving fast and keeping your design malleable!