When I get a failing test, I always figure out the reason for failure before doing a forced install. Even when there is only one failure of hundreds of tests, it can indicate a deeper issue, which I don't want some small problem to come back and bite me in the future. It is much easier to debug things when one has the indicator of a failure. Then, once I've figured out the reason for the problem, I'll report it to the author.

While any module with net-based tests often have failures due to changing test data, it still is important to understand why tests fail, as there can be no simple algorithm to say things are OK.

-a

In reply to Re: Test Failure Best Practices, or when is it ok to "force install" by albert
in thread Test Failure Best Practices, or when is it ok to "force install" by Anonymous Monk

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.