The biggest problem affecting the venerable Test::Harness is that the parsing, analyzing, and presentation of TAP output has been so tightly coupled that people have found it very hard to do anything "unusual" with it. My primary goal has been to break that coupling so that you can do anything you want. So the TAPx::Harness uses the TAPx::Parser to parse and analyze results and it presents the summary. It's simple enough that you can now use anything else you want to present this information. So yes, the intermediate abstract test results are all available in a very easy to use format. So here's one simplistic way, for example, of just printing failed tests:

my $parser = TAPx::Parser->new( { source => 't/customers.t' } );
while ( defined ( my $result = $parser->next ) ) {
    print $result->as_string . "\n" if ! $result->is_ok;
}
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.