IMHO the far more important metrics here are whether you're testing everything, as in code coverage and so on.

Yes, you seem to understand what I'm trying to do: I want to test everything adequately (and part of that is code coverage). Portability is a very important concern. In fact, my main reservation about using $^X, system, Capture::Tiny, etc, (which is very similar to what I used to do for in-house releases for known platforms) is a concern, potentially unfounded, that I might artificially limit the platforms my distribution will install on. On the one hand, maybe I am worried for nothing, but on the other hand, I'd hate for my entire module installation to fail because a test for the script did not succeed, when the library itself would have tested and installed just fine.

Thanks for the link to your distributions that use a similar approach. Those CPAN testers matrices give me hope that I might be worried for no good reason.

I know there is more I could do, but a lesser desire is that I keep my finite efforts focused on the library itself, with proportionately less time spent on some 40-line script I am including as a useful afterthought. But, hey, that's software sometimes, I suppose.

In reply to Re^2: Portably unit testing scripts by wanna_code_perl
in thread Portably unit testing scripts by wanna_code_perl

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.