Testing for websites?

[Cody Fendant]

I appreciate the Perl culture of testing. But how do you do tests when your code runs a website?

I can't test every page of a website after I make a change to the underlying code, and anyway the code is complex, there are ads being served, some of the page is random, for variety, and the HTML guy might be working on the template at the same time.

Do people make special tests which return simpler values than whole pages? Or does website testing always require human QA testers clicking through pages in a browser?

[chromatic]

But how do you do tests when your code runs a website?

I know what output I expect, and I test for that.

(See Simplified HTML Testing with Mojo::DOM and Mech for an example.)

I can't test every page of a website after I make a change to the underlying code....

If you have code to generate every page, you can test every page.

[rjt]

You might want to have a look at WWW::Mechanize. It can definitely handle the heavy lifting of the testing automation.

You will probably also benefit from unit testing the lower layers of your application. Do all of your library functions have unit tests that (reasonably) cover all kinds of inputs, good or bad? Test::More is your friend, here. You can also play with Test::Simple if you're new to the Perl testing style.

You will still of course need some human QA (write a test plan for your testers that covers your requirements), but the automation can certainly help you catch coding errors more quickly.

[McDarren]

Hi,

I've not used it myself, but I suspect that WWW::Selenium might be what you are after.

HTH,
Darren