Dear Master Monks,
I have a web application I need to test, and wanted some advice before I start writing. I have two ideas that follow;

1. Custom Module:

• Contains all the functions I would like to test e.g. uploads, logging in, navigation etc.
• Tested via simple ok tests with Test::Simple or if it gets a bit more complicated, via Test::More
• Seperate program that uses this module to run the tests
• Create Module with Module::Starter

2. Perl Test files:

• Each .t is a test for a feature of the web application
• Seperate program that calls prove to run them all

I have recently bought Perl Testing: A Developer's Notebook and Perl Best Practices, so they will probably help me out on the finer points ;-)

I think that maybe 1. would be the best way to go, as it would be a proper module, easier to manage, but might duplicate testing, i.e. testing the test functions. But then again, you can't test enough.

I will probably be using a bit of WWW::Mechanize and HTTP::Recorder to start me off.

I know a lot of Monks would have been in the same situation as me at some point, so if one of you kind souls would put me on the right path, I would be very grateful.

Thanks,
Gavin.