in reply to Re^2: automated testing
in thread automated testing

When a program always generates a report (including smooth, uneventful execution) you run the risk of missing errors simply by glossing over the report.
That's why you put the important fact (pass/fail) in the Subject, or first line of the report.

Having to gloss over a report to find out whether it's about a failure or a success is wrong.

Of course, if you get a gazillion reports a day, you can automate that as well: just have an addition program reporting to you which reports were failures, successes or passes. Just make sure *that* report gets send every day.

Replies are listed 'Best First'.
Re^4: automated testing
by Anonymous Monk on Oct 29, 2010 at 19:15 UTC
    But...you don't care what passed; it is, in turn, wrong to get a gazillion reports per day. Handling passed cases (i.e., parsing the subject line for PASS or FAIL, etc.) is just additional overhead. I'm not saying don't LOG, I'm just saying don't NOTIFY on success.
[reply]
Re^4: automated testing
by Urthas (Novice) on Oct 29, 2010 at 19:17 UTC
    argh I forgot to log in. The reply from anonymous monk is from me, Urthas. Apologies.
[reply]

In Section Seekers of Perl Wisdom