-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$this->setExpectedException(): stacktrace is missing when no exception was not raised #5
Comments
stack trace is missing e.g. in cli in the non-verbose mode. |
noticed in PHPUnit 3.4.14 |
a workaround is: But this is very bad "verbose code". |
This happens because The solution for this is to make note of the stack trace at the moment I've created a topic branch that solves this issue here: http://github.com/whatthejeff/phpunit/tree/issue_5. I'll send a pull request. |
Merged, thanks. |
On what date (or week or month) do you plan to release 3.5.0? |
It is not listed here (*) that issue 5 is part of release 3.5.0, please update, or did i misunderstand you? |
You can actually get 3.5.0RC2 (which contains this fix) with the PEAR installer. Try this:
|
There's also http://github.com/knplabs/phpunit-easyinstall if you don't want to use the PEAR installer. |
Works, good job. Thanks. |
I expect to have the test methods name and test methods line number in stack trace, when a expected exception was not raised on the test method where i used the setExpectedException() method. Would be great if we can have the line number of the setExpectedException() call also in the stack trace.
The missing stack trace (and missing line numbers) makes my IDE (netbeans) unable to navigate to the failing test method by clicking on the failing test in the "Test Results" windows.
The text was updated successfully, but these errors were encountered: