> I specifically left that out. It's an issue that Test::More deals > with, but doesn't have to. TAP.pod really only deals with > TAP, not the libs that create it.
Sort of. 1. qq{will generate FAILED tests 1, 3, 6 Failed 3/6 tests, 50.00% okay} That's T::H output. 2. qq{Currently Test::Harness does nothing with the description but we plan to use it in summary.} T::H specific, not relevant to TAP. 3. qq{Anything else Test::Harness will silently ignore any other output it sees but this behavior is not guaranteed in the future. If you want to place additional output in your test script, please use a diagnostic line.} T::H specific, not relevant to TAP. In fact, I'd say this is a bug in T::H, and the specification should be written so that any non-conforming output from a test that's supposed to be TAP compatible indicates a bug in the test program, and should be treated as though the test program (and all the tests it contains) have failed. N