After thinking about Daniel Risse's idea for a Test::Terminated module, I've been thinking this is something which should be incorporated directly in TAP. Plans become optional but the last line of the TAP output MUST be something like:
> tests finished That won't catch iterative tests misbehaving but it will catch a premature exit. In fact, if you have a bunch of cleanup code which fails *after* your last test is run (clean up temp files and so on) and those exit incorrectly, you catch that, too. We could add this onto TAP right now and it shouldn't break anything since Test::Harness ignores lines it doesn't understand, right? Of course, this presupposes that folks aren't completely burned out on TAP work for the time being (if you're not burned out, I would still LOVE feedback on the TAPx::Parser and whether or not that could be a candidate for the new TAP parser). Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/