I've written a Perl module which includes a Perl script to exercise the packaged functionality. The module has unit tests, some of which test the script: execute it via the "system" call and compare outputs to pre-recorded data. On my Linux machine, all the tests pass, so I uploaded the module to CPAN.

Unfortunately, when CPAN tests my module some more, its unit test often fail - it looks like they don't work anywhere but on linux, and while the specific failure reports aren't exactly the same, all agree that it's the script which won't run. So, what should I do with it? I can't take the script out - it's really necessary for the module to be useful. I suppose I don't have to test it, but that's a cop-out... Surely lots of people are including scripts with their Perl modules - is there some special way to package them?


In reply to How to unit test a script packaged in a module distribution? by vbar

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.