- All Superinterfaces:
- Functional Interface:
- This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.
AfterTestExecutionCallbackdefines the API for
Extensionsthat wish to provide additional behavior to tests immediately after an individual test has been executed but before any user-defined teardown methods (e.g.,
@AfterEachmethods) have been executed for that test.
Concrete implementations often implement
as well. If you wish to have your callbacks wrapped around user-defined
setup and teardown methods, implement
AfterEachCallback instead of
Consult the documentation in
Extension for details on
JUnit Jupiter guarantees wrapping behavior for multiple
registered extensions that implement lifecycle callbacks such as
That means that, given two extensions
Extension1 registered before
Extension2, any "before" callbacks implemented by
are guaranteed to execute before any "before" callbacks implemented by
Extension2. Similarly, given the two same two extensions registered
in the same order, any "after" callbacks implemented by
are guaranteed to execute after any "after" callbacks implemented by
Extension1 is therefore said to wrap
afterTestExecutionCallback that is invoked immediately after an individual test has been executed but before any user-defined teardown methods have been executed for that test.
context- the current extension context; never