Test failures are to be expected. Ideally, we would like to be able to install a module with no problems. That hasn't been my experience. I'd say %50 of the modules that I have installed have been problematic. The suggestions in the other replies are great--Read the Readme, Install, etc. pods. Debug, rerun the tests, but, for me, I always go back to the Makefile.PL and tinker with it until it looks right to me. Then install the module with make -ik, make -ikt; make test -ik, make test -ikt; make install -ik, make install -ikt. Sometimes I rerun make as: "make -B", then start the procedure all over again. I wish there was an easier way(smile)...

In reply to Re: Test Failure Best Practices, or when is it ok to "force install" by Khen1950fx
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.