Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re^3: When 100% Code Coverage Backfires

by xdg (Monsignor)
on Mar 26, 2007 at 16:07 UTC ( #606606=note: print w/replies, xml ) Need Help??

in reply to Re^2: When 100% Code Coverage Backfires
in thread When 100% Code Coverage Backfires

Nope. The point is to produce a better product.

Agreed. I think I phrased it poorly.

What I meant to suggest is that changing code for the primary purpose of increasing coverage is probably not the best thing to be doing, particularly if it makes the resulting product worse. Fixing defects or cleaning up code smells uncovered while working to improve coverage is -- as you pointed out -- part of the point of doing coverage testing in the first place.

Since I generally try to follow test-driven development, I aim for 100% at the start and decreasing coverage is a helpful sign that my coding has gotten ahead of my testing.


Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

  • Comment on Re^3: When 100% Code Coverage Backfires

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://606606]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (5)
As of 2022-08-12 06:32 GMT
Find Nodes?
    Voting Booth?

    No recent polls found