--- chromatic <[EMAIL PROTECTED]> wrote:

> Running tests or not running tests or ceasing to run tests as they're
> running is *not* T::B's problem. 

Could you please send Schwern a patch to remove all traces of the
BAIL_OUT functionality?

> You cannot solve it reliably at the T::B level.

That's like saying (pre < TH 3) that we can't have test GUIs in Perl
because you can't write them reliably with TH.  Just because
Test::Builder is has been written to be so inflexible does not mean
that the idea itself is bad.
  
> You can't even guarantee that the TAP you get comes from T::B, or
> Perl 5 ...

... which is completely orthogonal to the problem.

People aren't asking for a new feature of TAP.  They're not asking for
TAP behavior to be altered.  This has nothing to do with TAP.

They're just saying "hey, stop my test program/suite."  This is made
even more clear in Test::Most when a test program dies and the plan is
not fulfilled, you get a TAP parse error because of a bad plan.  If
alternate TAP producers don't want to implent die/bail on fail, so
what?  As long as they aren't producing incompatible TAP, it's OK TO
HAVE DIFFERENT FEATURES.

> If you want to stop running a long test suite when it produces 1 .. n

> failures, do it in the code that *runs* the test suite.

This is not a black and white issue.  Like the whole "all tests in
separate processes" debate which went on a while ago, you can make
reasonable arguments for each case:

1.  The code which runs the tests should also stop them.
2.  The tests should control their own behavior.

I think *both* arguments have merit and I welcome alternate solutions. 
JFDI.  If Andy implements the command line feature, that would obviate
a some of the current need for Test::Most and that would be a GOOD
THING.

Though about those deferred plans and YAML diagnostics.  Hmm ... :)

Cheers,
Ovid

--
Buy the book  - http://www.oreilly.com/catalog/perlhks/
Perl and CGI  - http://users.easystreet.com/ovid/cgi_course/
Personal blog - http://publius-ovidius.livejournal.com/
Tech blog     - http://use.perl.org/~Ovid/journal/

Reply via email to