----- Original Message ---- > From: Gaurav Vaidya <gau...@ggvaidya.com>
> As I understand it, the idea behind the final 'not ok' isn't as an > additionally > failed test, but as a way of forcing the plan to fail. That'll work as long > as > you don't have 'N' tests, and exactly 'N-1' tests finish before the suite > exists > prematurely - in which case we *still* tell the user something went wrong, > but > now you can't tell it apart from a single, failed test. Good point! > > 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. > How would such a UI handle situations where all the tests pass, but the plan > fails (too many tests, too few tests or a missing plan)? If those become > flashing/stripped lines as well, then the current spec works as written. If > not, > we should fix this up. It's all up to whomever implements it. TAP should provide information, not dictate its usage. 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
