Test Coverage Debate

Comments debate the value and limitations of code/test coverage metrics, arguing that 100% coverage does not guarantee correctness, thorough testing, or bug-free code, while highlighting it as a misleading proxy for quality.

πŸ“‰ Falling 0.5x Other
2,800
Comments
20
Years Active
5
Top Authors
#2076
Topic ID

Activity Over Time

2007
1
2008
5
2009
36
2010
27
2011
56
2012
75
2013
96
2014
119
2015
129
2016
153
2017
246
2018
159
2019
221
2020
226
2021
259
2022
263
2023
233
2024
264
2025
219
2026
13

Keywords

REPL www.cs STL MANY cmu.edu EVERY SmallTalk ICSE TOSEM CTL coverage code test tests 100 test suite testing spaghetti unit test suite

Sample Comments

mmjaa β€’ Nov 18, 2019 β€’ View on HN

Code coverage is not all you should be doing.

rgoulter β€’ Sep 1, 2020 β€’ View on HN

What's the value in code coverage from failing tests?

axod β€’ Feb 4, 2009 β€’ View on HN

You can have 100% code coverage, and still not be testing anything. Unless you're testing thoroughly the right parts, they're a false sense of security.

mempko β€’ Mar 20, 2021 β€’ View on HN

test coverage is not necessary for catching bugs in a line of code. There are other methods.

dusklight β€’ Mar 25, 2014 β€’ View on HN

why are you not crazy about good code coverage?

joosters β€’ Jun 4, 2020 β€’ View on HN

100% code coverage does not mean a full test suite. You can still find huge numbers of bugs in code that has 100% coverage in a test suite. The two are not the same!

andai β€’ Apr 13, 2018 β€’ View on HN

Pushback on increasing test coverage?

wojt_eu β€’ Oct 9, 2014 β€’ View on HN

100% code coverage still doesn't give you correctness.

ghayes β€’ Feb 14, 2018 β€’ View on HN

Be careful that coverage is a proxy metric to good tests. Striving for high coverage can mislead you on the quality of your tests.

o-__-o β€’ May 17, 2021 β€’ View on HN

They do, if you don’t have 100% code coverage then you get what you get