As with any code, you should test your objectives. When you wrote your nice httpd what did you set out to achieve? Test these things.
You should test the features that your httpd provides, as well as those aspects of the HTTP specification that you claim to support. Ideally, you would also test how your httpd responds to requests it can't deal with. The HTTP Implementor's Forum might help you.
LWP::Simple will allow you to perform simple tests (as its name suggests!), but you won't be able to use HTTP's POST method. I would suggest you investigate Test::WWW::Mechanize.
Finally, you might want to test your httpd against the behaviour of common browsers using Win32::IE::Mechanize or the WWW::Mechanize::Shell modules.
| [reply] |
Post a link to it on /. saying "This is the funniest thing I've seen in ages". :)
Don't expect to get any surfing done for a few days if your running off the same IP though.
Examine what is said, not who speaks.
"But you should never overestimate the ingenuity of the sceptics to come up with a counter-argument." -Myles Allen
"Think for yourself!" - Abigail
"Time is a poor substitute for thought"--theorbtwo
"Efficiency is intelligent laziness." -David Dunham
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon
| [reply] |
I think generally you want to test:
if the correct content is returned on a request
you want form input to be handled correctly
you might want some performance test (use apachebench, /usr/sbin/ab2 on an apache2 box).
Depending on what kind of webapp you have you might want to test more. | [reply] |
What is a nice httpd and why does it need testing? | [reply] |
| [reply] |