Ovid wrote:
I don't think much special work would need to be done. I've heard that Test::Cmd
works pretty
well. I was reading that just a few days ago, but I can't remember where I read that
(grr ...)
I mentioned it a few days ago because it designed to deal with
command-line programs, but I
It occurs to me that that if I wanted to build a health check
watchdog for my system (a script that executes at regular intervals
to ensure proper operation), that the Test::* mechanisms would
be pretty ideal for checking the results and reporting the proper
errors.
I can't be treading new
My initial thought would be simply to have a series of test programs to verify
everything that you
need. Then set up a cron job and just run 'em through Test::Harness and pipe the
output to your
favorite mail program.
perl -MTest::Harness -e 'runtests(glob /path/to/tests/*.t)' 21 | mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Randal L. Schwartz merlyn at stonehenge.com [2003-07-21 13:21]:
It occurs to me that that if I wanted to build a health check watchdog
for my system (a script that executes at regular intervals to ensure
proper operation), that the Test::*
Darren == Darren Chamberlain [EMAIL PROTECTED] writes:
Darren * Randal L. Schwartz merlyn at stonehenge.com [2003-07-21 13:21]:
It occurs to me that that if I wanted to build a health check watchdog
for my system (a script that executes at regular intervals to ensure
proper operation), that
