Well, what I'd say more than anything else is: put as little logic as possible in your scripts. Make them just executable wrappers around your modules, and then write test cases for your modules.

Beyond that, yes, it would be cool to have script harnesses (although, my limitted experience with IPC::Run would lead me to recomend it over IPC::Open3).

Last, as for testing web servers: what we do where I work is we actually wrote a web replay agent, which reads in apache logs and issues requests to the web server, logs the output and diffs it against the expected results. We've been trying to push the idea to management of getting this test harnass released to open source... but no luck yet. Anyway, the idea is pretty straight-forward, though. 

------------
:Wq
Not an editor command: Wq

[download]

In reply to Re: A test harness for scripts by etcshadow
in thread A test harness for scripts by rinceWind

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.