comment on

I have boiled it down to this demo. TAP::Harness looks like the best driver and it has a callback that lets me get at the parser before it would otherwise be used. Silencing the harness means that it never gets to find out that its parsers have been drained.

use TAP::Harness;

my $harness = TAP::Harness->new( { verbosity => -3, merge => 1 }  );
my @tests = glob "t/*.t";

$harness->callback( made_parser => \&hijack_parser );
$harness->runtests( @tests );

sub hijack_parser
{
  my ($parser, $test_ref) = @_;
  while ( my $result = $parser->next )
  {
    $result->is_test or next;
    $result->is_actual_ok and next;
    (my $description = $result->description) =~ s/- //;
    print "I seem to have failed $description in $test_ref->[1]\n";
  }
}
[download]

Peter Scott
Perl Medic

In reply to Re^3: Intercepting TAP output by peters
in thread Intercepting TAP output by peters

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks