I find this really useful, thanks. I'm using it as a consequence of the sitation I described in Reporting test failures within cron.
I noticed it doesn't work quite right if I run an incorrect number of tests. For example:
use Test::More tests => 3;
ok 1, 'Happy';
ok 1, 'Cheerful';
We expect three tests but only run two, which both succeed. Fortunately, is_expected deals with this, but unfortunately show_details doesn't report the failure. The altered is_expected_test_result below fixes this reporting problem:
sub is_expected_test_result {
my $test_result = shift;
return $test_result->{ok} &&
! is_unexpected_todo_success( $test_result ) &&
! diagnostics( $_ );
}
I discovered this when running some Test::WWW::Mechanize tests against a server that stops responding, causing later tests not to run.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|