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.

[download]

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 below.

Cheers,
Ovid

New address of my CGI Course.

In reply to Need advice on test output by Ovid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.