Gabor Szabo wrote: > You to write a bunch of test with the standard Mechanize API and then run > them either using Test::WWW::Mechanize::CGI *without* a web server > or using Test::WWW::Mechanize after setting up a the application with > a real web server.
I agree with Gabor here. If I'm writing a standalone module (like one I'd release to CPAN) I would probably use something like Test::WWW::Mechanize::CGI without a server. But if I'm testing a project that is designed to run on a certain platform with a certain web server, then I'd test it with the webserver and Test::WWW::Mechanize (along with Test::HTML::Content). To do this, you'll need to create your own test harness that starts the webserver and then runs the tests, but that's simple enough with Test::Harness and even simpler with the new TAP::Harness. One thing I'm experimenting with (and I'll hopefully talk about at YAPC if my talk get's accepted) is using Selenium IDE as the starting point to write web tests. And hopefully soon, I'm going to try to get the business folks involved in creating those tests too. -- Michael Peters Developer Plus Three, LP --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
