Code Coverage Article
Every once in a while in this age of Aquarius, a conversation about coverage reports would leave me motivated to write an article elaborating their dangers. Too often I find them misused as indicators of “test quality†or developer productivity. Similarly, I’ve yet to run across a traditional QA manager who was aware of these reports, much less of their copasetic implications.
I finally put something together in a new series on code quality. Check it out and feel the funk on DevWorks.
| Related odds and ends | ||
|---|---|---|
| ||
Saturday 04 Feb 2006 | Articles
[...] A metric, in and of itself, is not very useful– for example, code coverage is simply a number that, in isolation, doesn’t mean anything. Highly covered code is still susceptible to defects! Coverage also is not an indication of test quality, by the way. Coverage is simply a measure of test execution– what’s important is how the coverage values are utilized and compared against other hip metrics or trends. [...]