Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:
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?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Automating CGI Testing
by adrianh (Chancellor) on Sep 17, 2003 at 14:48 UTC | |
|
Re: Automating CGI Testing
by Corion (Patriarch) on Sep 17, 2003 at 14:57 UTC | |
|
Re: Automating CGI Testing
by tcf22 (Priest) on Sep 17, 2003 at 14:49 UTC | |
|
Re: Automating CGI Testing
by drfrog (Deacon) on Sep 17, 2003 at 19:01 UTC |