|Do you know where your variables are?|
Reporting test failures within cronby tomhukins (Curate)
|on Sep 13, 2005 at 11:34 UTC||Need Help??|
tomhukins has asked for the
wisdom of the Perl Monks concerning the following question:
I've written some simple tests with Test::WWW::Mechanize that check a Web site behaves as it should.
I am running these tests within cron, which sends me messages that look like:
If I alter cron to run the test script through prove I get briefer output:
Ideally, I would like cron to only send mail if any tests fail. I could write a wrapper script to deal with this, but I wonder if you can think of a neater way?
I also wonder if I can easily report when the script didn't run at all. In this case, no tests will fail, but I still care about what happened.
Over time, I expect to add more tests in different scripts. For a collection of tests, does it make sense to write a Makefile.PL or can I get away with something like prove /path/to/*.t?
I'm looking for a clean and simple approach. Tools like Nagios look helpful, but seem like overkill for this problem to me. Any thoughts?