On 22 Sep 2006, at 09:11, Ovid wrote:
I don't have time to track this down, but I've noticed the
following when I run my Test::Class tests through prove:
[snip]
As you may notice, you see the diagnostics from the TODO failures.
As Schwern has noted repeatedly:
The user should not see the diagnostics from that TODO failure.
[snip]
I've not been able to reproduce this, e.g.:
----
#! /usr/bin/perl
# spoon.t
use strict;
use warnings;
{ package My::Test;
use base qw( Test::Class );
use Test::More;
sub there_is_no_spoon : Test {
local $TODO = "perceive true nature of reality";
is bless( {}, 'Spoon' ) , undef;
}
}
Test::Class->runtests;
----
% prove t/spoon.t
t/spoon....ok 77 ms
All tests successful.
Files=1, Tests=1, 0 wallclock secs ( 0.05 cusr + 0.01 csys = 0.06
CPU)
So I'd be interested in a test case.
[snip]
And is there any way that displaying the diagnostics from TODO
failures can break things (such as making it difficult to install
modules)?
[snip]
I can only think of it causing problems for testing test modules that
output todo tests - where you might be capturing the output from
STDERR explicitly - moderately uncommon I would think.
Adrian
