Andy Armstrong wrote: >> That really requires me to collect all the data for this table and >> then send it to diag. I think I would prefer to output it line by line >> as the test runs, maybe with other calls in betwwen: > [snip] > > Well of course there's nothing to stop anyone writing code that collects > items to be output as YAMLish in the way you describe - and there's > nothing to stop them releasing it as a module :) > > This is really something that the producer's going to have to do and we > haven't actually talked much about what's going to happen on the TAP > producer side but I imagine something as specific as building a table > will be outside the scope of Test::More.
Yes, quite. That's the idea of this whole revamp of TAP. Push more control down to the individual and out of a monolithic module (aka Test::Harness) both to allow customization as the user desires and so that TH and TAP::Parser don't have the (impossible) task of pleasing everyone. So the answer is yes, YOU can do it. There's the data, do whatever you like with it. Its a similar shift as when Test::Builder came around and allowed anyone to build their own Test module. People still try to wedge everything into Test::More anyway.
