Well, what's the point in having your module pods (not just coverage) tested on every machine where it is installed?

Running tests on the target machine allows to discover portability problems and bugs that didn't show on the module author environment. But pods are just documentation, they are not affected by the environment, if they were right on his computer when he tested them before packing the module, they are going to be the same on the target system, so why bother testing them and actually introducing new code that, as in your case, can contain new bugs? it is just counterproductive!

A good aproach could be to skip pod tests unless they are explicitely requested by the user installing them, for instace defining some enviroment var (TEST_PODS) or looking for some dummy file on the file system.

In reply to Re: Careful with Test::Pod::Coverage by salva
in thread Careful with Test::Pod::Coverage by xdg

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.