TAP version 13

elTriberium has asked for the wisdom of the Perl Monks concerning the following question:

Hi Monks!

I'm very much interested in the YAML blocks of TAP version 13: http://testanything.org/wiki/index.php/TAP_version_13_specification

It looks like the initial specification was already done on 2007/03/17. However, so far I haven't found a single module which produces these blocks. It would be very cool if modules like Test::More / Test::Exception would produce this kind of output for all negative test results, so that they can easily be parsed by a test harness.

I already produce some YAML output myself with TAP::Parser::YAMLish::Writer, but this doesn't include the output by the Test:: modules. Of course I could subclass those modules and overwrite the particular methods to generate YAML output. But this would make my code less portable, which I also don't like too much.

So my question is: Does anyone know of a module which might already do this or is currently in development?

Comment on TAP version 13

Replies are listed 'Best First'.
Re: TAP version 13 by Anonymous Monk on Jul 12, 2011 at 00:44 UTC
Of course I could subclass those modules and overwrite the particular methods to generate YAML output. But this would make my code less portable, which I also don't like too much. Upload to CPAN, and your code is now portable :) So my question is: Does anyone know of a module which might already do this or is currently in development? According to that wiki, taps-testing - Testing .NET and Mono software using TAP has a yaml writer :D But I don't really follow the qa/tap... development that closely :) See this thread JSON TAP Diagnostics? for some reasons why it probably doesn't exist :)	[reply]
Re^2: TAP version 13 by elTriberium (Friar) on Jul 12, 2011 at 08:18 UTC
According to that wiki, taps-testing - Testing .NET and Mono software using TAP has a yaml writer :D Too bad it's .Net and won't help me ;) See this thread JSON TAP Diagnostics? for some reasons why it probably doesn't exist :) Well, that's the point I don't really understand. About 3 years ago there were a lot of discussions about adding this cool feature and since then nothing happened? I was under the impression that the whole testing infrastructure is one of Perl strengths with the Test:: and TAP:: modules, but in this area it looks like nothing is going on. Don't get me wrong. I understand that most people working on CPAN modules are doing this in their free time and of course I'm not in the position to demand a particular module, but I just don't understand why this effort has stalled in the last 3 years. I'm hoping someone who participated in that original discussion will read this post :)	[reply]


laziness, impatience, and hubris
	PerlMonks