This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: the danger of full-coverage lust
Feed Title: Logemann Blog
Feed URL: http://www.logemann.org/blojsom/blog/default/?flavor=rss2
Feed Description: Marc's thoughts on Java and more
I like statistics, i like them in sports, when doing homebanking and of course also when writing software. Tools like Clover or JCoverage are thus nice thingies. But there is some inherent danger, the danger of wanting to reach 100% or near 100% in your projects. I think this tends to let people write a lot of tests only to have nice coverage in the first place. Companies forget that its not only about the coverage solely but the quality of the tests itself. I would rather have only 80% of coverage but these 80% are really real world tests and not only "we have to somehow cover these lines too"-tests. The problem is due the fact that management like numbers and when you have a range from 0-100 (where 100 is the best value), sooner or later you will get the call to reach, lets say, 90% no matter what.
Previous Topic
