----- Original Message ---- > From: Eric Wilhelm <scratchcomput...@gmail.com>
> >For example, if a test program knows that it is going to > >exit abnormally, even after it has finished emitting TAP according to > > its plan, it should emit one final "not ok" line before exiting. > > So, > > 1. TAP::Harness should store that when archiving? > 2. Is it possible to have something more explicit than that? (or does > the exit code go in the test name or what? The current discussion has generally been along the lines of "Core TAP should be all that is needed to know if tests have passed or failed". Thus, Schwern's 'not ok' final line meets this criteria. That being said, 'not ok - test exited prematurely' is not terribly structured and doesn't necessarily let an advanced TAP consumer present this information any better. Structured TAP diagnostics (preferably in JSON and not feasible with the current Test::Builder) would be an optional feature which would allow additional information to be passed. It shouldn't affect pass/fail status, but instead augment that status to allow the TAP consumer to respond appropriately, if needed. As an example, someone writing a test runner GUI could have standard green/red pass/fail lines, but maybe have flashing or striped red lines for premature exits, letting the programmer prioritize what he/she needs to deal with. The key here is to make all of this optional (as much as is feasible), but possible. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
