Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re: Reporting test failures within cron

by Hue-Bond (Priest)
on Sep 13, 2005 at 12:30 UTC ( #491561=note: print w/replies, xml ) Need Help??


in reply to Reporting test failures within cron

I am running these tests within cron
Ideally, I would like cron to only send mail if any tests fail.

cron only sends mail when output is generated. What you want is that your tests be silent if everything goes ok (ie: change your print statements or redirect STDOUT) and direct error messages to STDERR. That way, you can control whether you want all the output (by not redirecting STDOUT) or only errors (ideally none -> no output -> no mail from cron).

--
David Serrano

  • Comment on Re: Reporting test failures within cron

Replies are listed 'Best First'.
Re^2: Reporting test failures within cron
by tomhukins (Curate) on Sep 13, 2005 at 12:40 UTC
    That's true, but as I'm using Test::WWW::Mechanize with Test::More I don't output anything myself directly: the testing tools do this for me.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://491561]
help
Chatterbox?
[stevieb]: I think that placing the * in C when dealing with pointers is akin to keeping separated the circumfix op from the inner ref in Perl: @{ $aref };, which is all personal preference. In perl, I'm good. C, don't know what I like
[stevieb]: ...yet. Still too newbie

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (6)
As of 2017-01-24 02:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you watch meteor showers?




    Results (200 votes). Check out past polls.