ghenry has asked for the wisdom of the Perl Monks concerning the following question:
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 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 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.
Fancy a email@example.com? Just ask!!!