On Wed, 2004-04-07 at 00:23, Leopold Toetsch wrote:
> $ perl -Ilib t/pmc/object-meths.t
> 1..17
> ...
> not ok 17 - constructor - diamond parents # TODO wrong init order?
> # Failed (TODO) test (t/pmc/object-meths.t at line 469)
> ...
>
> $ perl -Ilib t/harness t/pmc/o*.t
> t/pmc/object-meths....ok
> t/pmc/objects.........ok
> t/pmc/orderedhash.....ok
> All tests successful.
> Files=3, Tests=72, 2 wallclock secs ( 1.15 cusr + 0.60 csys = 1.75 CPU)
>
> It's suboptimal that the summary doesn't cover the TODO test. There is no
> sign that something is wrong.
That's a longtime feature of Test::Harness. It will report any TODO
tests that unexpectedly succeed:
$ cat todo_tests.pl
#! perl -w
use Test::More tests => 2;
TODO:
{
local $TODO = 'todo these';
ok( 0 );
ok( 1 );
}
$ perl -MTest::Harness -e 'runtests( "todo_tests.pl" )'
todo_tests....ok
1/2 unexpectedly succeeded
All tests successful (1 subtest UNEXPECTEDLY SUCCEEDED).
Files=1, Tests=2, 1 wallclock secs ( 0.05 cusr + 0.01 csys = 0.06
CPU)
$
It's possible to customize this, if you want, or to write a tool looking
for TODO tests, but this is the default, expected behavior.
-- c
