Shlomi Fish wrote:
"t/sample-tests/todo" in the Test-Harness distribution reads:
<<<<<<<<<<<
print <<DUMMY_TEST;
1..5 todo 3 2;
ok 1
ok 2
not ok 3
ok 4
ok 5
DUMMY_TEST
As one can see, the "1..5" plan is followed by the "todo 3 2;" directive.
This is supposed to indicate something about plan ahead todo tests. (Instead
of the "# TODO" directives in the individual tests' outputs. Now:
1. t/sample-tests/todo is being run by Test-Harness, which seems to think
the "not ok 3" is a todo test.
2. This todo-enabled plan is not documented in:
http://search.cpan.org/~petdance/Test-Harness/lib/Test/Harness/TAP.pod
3. TAPx-Parser version 0.20 cannot handle it.
--------------
I'd like to know what I should do about this feature, because right now I'm
trying to convert Test-Run to use TAPX::Harness, and this is giving me
problems.
These "old style" todo tests were never really documented until I stumbled on them inside Test::Harness and Test.pm, nobody really understood, aren't very useful and weren't really used.
They were deprecated a while ago. Since they were never really documented or
used I just hid the deprecation notice inside Test::Harness as it was only
interesting to folks hacking on it. This notice used to appear in
Test::Harness but it appears to have been removed.
=begin _deprecated
Alternatively, you can specify a list of what tests are todo as part
of the test header.
1..23 todo 5 12 23
This only works if the header appears at the beginning of the test.
This style is B<deprecated>.
=end _deprecated
Don't push them forward into TAP. Any feature which relies on static test
numbering is broken. Just let them die.
