Another interesting concept is how Kate Pugh does the test setup with CGI::Wiki - a module CGI::Wiki::TestConfig is created and installed with database server credentials by asking the user some questions, unless it already exists. This allows to have persistent test data even across installs and makes testing the stuff where a server is needed even more automatable.
Another method I found for testing CGI scripts was to set up a mock CGI object (via Test::MockObject) and to simulate my requests to my script through that, but this strategy won't help you much, as you will want to check that your LDAP database was indeed modified as you planned.
Personally I also want all tests to be run by default. If they take too long for someone, they should turn to the README on how to cut down testing or simply skip testing at all - if you believe the module works, there is no need for testing.
perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ; # The
$d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider
($c = $d->accept())->get_request(); $c->send_response( new #in the
HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' # web
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.