I've had some very good success with the Test::Cmd distro, when testing commandline stuff. I used it to test something that was going to be run in a batch mode, ending up with over 200 tests in less than a month of ad-hoc development. This works equally well for commandshell and batch, cause batch is really just commandshell w/o an active user.

As for web scripts, I've been getting some good traction using a combination of the following:

  1. Structure the application using CGI::Application and with good modularization. Standard 'make test' works for the API. (My current app is split into 9 CPAN-like distributions and one catch-all install including the templates, CSS, and C::A bootstrap scripts.)
  2. WWW::Mechanize, which not doing look-and-feel very easily (you have to source-dive the HTML) and not handling JScript events (you have to implement them yourself in the test script), it does do a good job of spot-checking the result. Plus, it nicely handles redirects and the like.

Good luck!

------
We are the carpenters and bricklayers of the Information Age.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re: A test harness for scripts by dragonchild
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.