Test framework integration overview

Abort-Mission Boosters aim to integrate with your test framework (e.g. JUnit Jupiter) in order to monitor how your test class post processing and test execution is working.

Obviously there are inevitable differences due to the smaller or larger differences between test frameworks but the generic approach taken by Abort-Mission remains the same. Please find this approach illustrated below on the sequence diagram showing the pseudo integration.

It is worth mentioning, that since v2.0.0, Abort-Mission handles per-class type test instance lifecycle better than before (for example JUnit Jupiter PER_CLASS lifecycle or the default TestNG approach). This means, that the countdown and mission counters are handled separately, allowing us to register class level events for countdown while method level events to mission only.