Skip to content

li3 verbose does not show all exceptions in case of fatal #517

Open
hans-d opened this Issue Jun 2, 2012 · 4 comments

2 participants

@hans-d
hans-d commented Jun 2, 2012

Playing around with testing, and probably my set up is not yet complete. I have multiple lines reporting having an exception, but I get no useful information, such as: the exception raised, and its context.

[exception] on line   14 in app\controllers\RelatieAppService::startNieuweRelatie()
[exception] on line   86 in -::session_start()
[exception] on line   86 in -::session_start()
[exception] on line   25 in app\controllers\RelatieAppService::startNieuweRelatie()
[exception] on line   25 in app\controllers\RelatieAppService::startNieuweRelatie()

Fatal error: Unsupported operand types in [...]\app\controllers\RelatieAppService.php on line 25

Call Stack:
[...]

The fatal error I could trace down to a non-existing variable...

Normally all exceptions are shown.

@davidpersson
Union of RAD member

You cannot recover from or catch fatal errors. Without the fatal error the test would've been continued to be executed. Later - after all tests - you'd be given a summary along with stack traces for each fail/exception. You're not seeing this because the script aborts at the fatal.

I don't see any other way handling this also it appears to me to be expected behavior. Feel free to reopen with ideas for other ways to handle this. Thanks for your report.

@hans-d
hans-d commented Jun 3, 2012

Perhaps the execptions can already be shown when they are captured. Perhaps something for a --verbose=immediate ?

This mode could also be that under the failed test line the results of the fail are directly displayed.

(and something small, could in verbose mode also the time of the testline be displayed? helps for digging in any logs)

@davidpersson
Union of RAD member

Noted :)

@davidpersson davidpersson reopened this Jun 4, 2012
@davidpersson davidpersson was assigned Jun 4, 2012
@hans-d
hans-d commented Jul 10, 2012

related to #481. Shall we name the flag immediate, or does it belong under one of the flags already mentioned in #481 (comment)

@davidpersson davidpersson modified the milestone: future Sep 30, 2014
@hans-d hans-d removed this from the future milestone Sep 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.