I'm refactoring a CGI web-site, and I want to create a test suite for the site as a whole (as opposed to just unit tests). My thinking is that this would both give me a way of detecting if my changes are introducing bugs and perhaps find currently undiscovered problems. It would also allow testing from remote locations so that, if something goes down, I could localize it without leaving my bedroom.

Is there any standard way of going about doing this? There is a CGI::Test module, but it has several limitations (no cookies) and hasn't been updated in a couple of years. I could see myself writing extensive LWP stuff to do this, but I'd prefer not to if it isn't necessary. How do other monks approach this?

In reply to Automating CGI Testing by Anonymous Monk

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.