Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Test-Exception CPAN distribution.

Report information
The Basics
Id: 29028
Status: resolved
Priority: 0/
Queue: Test-Exception

People
Owner: Nobody in particular
Requestors: pjs [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.25
Fixed in: (no value)



Subject: exit() causes test to not be run
An exit() in eval'ed code makes it look as though the test never existed. Test::Builder is able to keep going because of the END block in Test/Builder.pm. You might either document this as something to avoid, or override CORE::GLOBAL::exit locally in _try_as_caller().
On Mon Aug 27 20:54:24 2007, PJS wrote: Show quoted text
> An exit() in eval'ed code makes it look as though the test never > existed. Test::Builder is able to keep going because of the END block > in Test/Builder.pm. > > You might either document this as something to avoid, or override > CORE::GLOBAL::exit locally in _try_as_caller().
Good point. I think I'll go the document route - T::E already has a lot of magic in it, and the current behaviour is consistent with other test modules. Cheers, Adrian
On Mon Aug 27 20:54:24 2007, PJS wrote: Show quoted text
> An exit() in eval'ed code makes it look as though the test never > existed. Test::Builder is able to keep going because of the END block > in Test/Builder.pm. > > You might either document this as something to avoid, or override > CORE::GLOBAL::exit locally in _try_as_caller().
Documentation patch added in 0.26. Hitting CPAN as soon as pause starts working again.