I would extract a module from your script and unit test the module
directly via Test::More and the prove command.
I like to keep my script mainlines as short as is practicable,
with all the heavy lifting done in (unit-tested) module/s.
There are many examples of this general approach on the CPAN;
see, for example, the perltidy command,
part of the Perl-Tidy distribution
and the perlcritic command, part of the Perl-Critic distribution.
As an alternative, and perhaps a bit less work, you could
re-structure your script as a "modulino", that is, a script
that can masquerade as a module for ease of testing.
This approach is described at:
See also: How do you test end-user scripts?
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||