What helped is to move the functionality to modules, because IMHO modules are much neater to test than scripts.
True, but it doesn't have to be like that.
Keep the script, but encapsulate all code in subroutines except the last line below. The last line ensures that one can require the script without actually running its' contents.
I argue that this script is no harder to test than a module.
# script.pl
sub foo { ...; $retval; }
sub bar { ...; $retval; }
sub main {
foo() or die();
bar() or die();
}
# Call main only if no stack. Non-empty stack means we're testing.
# See chapter 9 of Perl Testing - A Developer's Notebook
main() unless caller;
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
