Re: How should a failing TAP::Harness result exit?

On 31 Aug 2009, at 21:27, David Golden wrote:
> Copying M::B and tapx lists as this is relevant to both groups.

(apologies - I'm away a lot at the moment and /very/ slow dealing with  
my mail)

> David Wheeler opened a ticket on Module::Build noting that
> Test::Harness dies on failure but TAP::Harness does not.  Thus, "Build
> test" with TAP::Harness active could have exit code 0 (success) even
> if things failed.

The rationale was that Test::Harness needed to do that to preserve  
backwards compatibility but that TAP::Harness should not - to make it  
easier to use in cases where you don't want to die.

> Alternatively, I could have Module::Build just die("Errors in testing.
> Cannot continue\n") instead of emulating the Test::Harness die
> message.


That seems reasonable to me.

-- 
Andy Armstrong, Hexten