Prevent tearDownAfterClass exceptions from killing PHPUnit #3490
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Found out yesterday that
tearDown[AfterClass]
exceptions were not handled byTestSuite
the way it does forsetUp[BeforeClass]
. PHP simply exits to the command line:This fix will report exceptions in
tearDownAfterClass()
by adding a dummy test at the end of aTestSuite
calledtearDownAfterClass
with the original message and stack trace. A corrected code location hint is added to the top pointing to the offending line.On the command line:
In IntelliJ it looks like this: