comment on

Excellent Meditation!

Let me start out by saying I admire your drive to get 100%, it is not an easy thing to do. Personally I think that 100% is (in most cases) overrated, and >95% is acceptable in most cases, but you make a good argument.

Of the things you said, I think this:

even if everything is tested, it might still be wrong

and this:

fixing the remaining bugs as they arise is made ridiculously easy in most cases, because it is so well tested. Fixes that break existing behaviour are highlighted as test failures - without test cases you might never know

are two of the most important points.

Test/Code coverage is no silver bullet, as the How to Misuse Code Coverage article pointed out. But as your next point says, it is sure nice to have those tests when you are fixing bugs.

Again, excellent post :)

-stvn

In reply to Re: Lessons learned from getting to 100% with Devel::Cover by stvn
in thread Lessons learned from getting to 100% with Devel::Cover by leriksen

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks