I'm a belt-n-braces coder, and I believe it is perfectly reasonable to have a test in one part of the code that will never be triggered unless at some point in the future another part of the code changes. But it is notoriously difficult to test that all possible error paths are correctly handled.

Consider whether it might make sense to split the routine into two - some methodologies would in any case consider it bad form to have a function that performs two operations. This would allow you separately to test that the first routine cleans the data, and that the second routine correctly barfs on bad data.

Hugo

In reply to Re: Devel::Cover, Testing, 100%?! by hv
in thread Devel::Cover, Testing, 100%?! by BUU

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.