Jupiter engine does not invoke 'afters' if exception is thrown by test or 'befores'

[sbrannen]

Status Quo

In contrast to the behavior of JUnit 4, the Jupiter TestEngine currently does not invoke any "after each" methods or callbacks if an exception is thrown during test execution or by a "before each" method or callback.

Related Issues

• Test execution exceptions are not supplied to extensions #92
• Jupiter engine does not invoke 'after alls' if exception is thrown by 'before alls' #359

Deliverables

• Ensure that "after each" methods and callbacks are invoked even if an exception is thrown by the test method or a "before each" method or callback.

[sbrannen]

in progress

[mmerdes]

The 'callSequence-technique' in the tests is quite helpful in aiding the understanding of what is going on.
To me, this understanding would be further eased if the labels were even more distinctive, i.e.
barBeforeEachCallback instead of barBeforeCallback etc