>From http://www.perlmonks.org/?node_id=593087:
I'm working on TAPx::Parser and trying very hard to make my
TAPx::Harness output as similar to Test::Harness output as is feasible.
I am doing this primarily because if the basic output is too different
from what folks are used to, the "strangeness" might discourage
adoption. However, petdance has said the following:
Please don't try to make it match Test::Harness. The
Test::Harness format is clunky and yucky. I've been
meaning to redo it for some time.
Maybe you can come up with something beautiful that
I can steal instead!
Well, the fact remains, I can't, and that's where I need your help,
Monks! Consider the following summary from a failed test run:
Failed Test Stat Wstat Total Fail List of Failed
------------------------------------------------------------------
t/bar.t 4 1024 13 4 2 6-8
t/foo.t 1 256 10 1 5
(1 subtest UNEXPECTEDLY SUCCEEDED).
Failed 2/3 test scripts. 5/33 subtests failed.
Files=3, Tests=33, 0 wallclock secs ( 0.10 cusr + 0.01 csys = 0.11
CPU)
Failed 2/3 test programs. 5/33 subtests failed.
I agree with petdance that this is rather clunky, but I'd love to hear
your feedback on how you'd really like to see that information. That's
what I'm working on right now and I'd love to get something that's more
useful for folks. Keep in mind that TAPx::Parser collects far more
information than Test::Harness, so if there's more stuff you'd like to
see, that's fine, too. I can break it down on a test-by-test basis and
show failed tests, unexpectedly succeeding tests, skipped tests, and so
on. However, this could be a lot of clutter.
What would be a good, easy-to-read format for this? Feel free to get
creative and post examples.
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
