Repository navigation
Exceptions in junit AfterAll / AfterClass are not reported as error since 3.5.5 #3412
Description
Affected version
3.5.5+
Bug description
see comment
the integration test added in #3338
documents the current (faulty?) behavior.
reverting b4a53de brings back the old behavior of reporting class teardown issues as errors.
why this matters:
- a lot of test infrastructure can do important things on class teardown i.e. check for resource leaks, clean up for the next test etc.
- even if intentional such a behavior change should not be introduced in a patch version imo
also note that when rerunFailingTestsCount > 0 passing tests are getting rerun on class teardown errors.
Activity
fix: report AfterAll/AfterClass exceptions as errors again (#3412) (#…
XN137 commentedon Aug 11, 2026
thanks for the fix, but i am wondering:
shouldnt this also get backported to
surefire-3.5.x?olamy commentedon Aug 13, 2026
sounds like a good idea see there #3427
please have a test and let us know if this is fixing your issue with 3.5.x branch
Report AfterAll/AfterClass failures as errors, not flakes (#3412) (#3427
XN137 commentedon Aug 17, 2026
since the fix copied the integration tests i had suggested for reproducing this problem, i am quite confident the issue has been addressed.
i will wait for the next 3.5.x release to confirm once more on our codebase.