Conditional Test Execution Pairs: @EnabledIfSystemProperty & @DisabledIfSystemProperty

Overview

In this lesson, we'll explore how Java system properties can drive the execution of tests in JUnit Jupiter. We provide a custom system property to the Run Configuration in our IDE, and verify that Jupiter will enable all tests annotated with @EnabledIfSystemProperty, given that the property's value matches the expectation inside the annotation. Conversely, other tests can be disabled using the same process, with @DisabledIfSystemProperty. We'll come to appreciate the verbose nature of the framework's logging once more, because the TestEngine will print statements to the console about the different reasons it chose to execute or skip a test.

Summary

• Configure Java system properties to drive test execution
• @EnabledIfSystemProperty checks the value of a property against a regular expression; only in case of a match, the element is executed
• @DisabledIfSystemProperty checks the value of a property against a regular expression; in case of a match, the element is never executed
• If a property doesn't exist at all, @DisabledIfSystemProperty methods are always executed