On 10 Dec 2007, at 16:41, Ovid wrote:
It's actually quite easy to do - just need to plug in a different
formatter. Plan == number of test files etc.
Regrettably, this is merely a gut feeling of mine. Think of the
'Result: PASS' we have at the end of our output now. That could go
away. Because we would use TAP::Parser to parse the TAP.
You'd still want human readable output in that case I think - so you'd
have to output both TAP and a normal summary. That's not much of a
problem - just thinking out loud.
Also, with the discussion of nested TAP, this means that individual
test results would get nested inside of the top level TAP. Slap on
some diagnostic information about the test run and reading and writing
TAP::Harness::Archive files (for example) becomes simpler.
Yeah, that'd be cool. Work is really needed on figuring out how the
API changes when you have nested blocks. There's a branch in the repo
that handles blocks from the grammar to about half way up the parser -
how the top half of the parser changes in the challenge :)
It'd probably be good to work that stuff out first.
--
Andy Armstrong, Hexten
