Custom conditions with @EnabledIf in JUnit - Build an Automation Script

Automate a test that runs only if a custom condition is true using @EnabledIf

Preconditions (2)

Step 1: Create a test method annotated with @Test and @EnabledIf

Step 2: Implement a static method that returns a boolean for the condition

Step 3: Annotate the test method with @EnabledIf referencing the condition method

Step 4: Run the test suite

Step 5: Verify the test runs only if the condition method returns true

✅ Expected Result: The test method executes only when the custom condition method returns true; otherwise, it is skipped.

Automation Requirements - JUnit 5

Assertions Needed:

Verify the test method runs when the condition is true

Verify the test method is skipped when the condition is false

Best Practices:

Use static methods for @EnabledIf conditions

Keep condition methods simple and side-effect free

Use descriptive method names for conditions

Use assertions inside the test method to verify functionality

Automated Solution

JUnit

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.condition.EnabledIf;
import static org.junit.jupiter.api.Assertions.assertTrue;

public class CustomConditionTest {

    @Test
    @EnabledIf("customCondition")
    void testRunsOnlyIfConditionTrue() {
        // This test runs only if customCondition() returns true
        assertTrue(true, "Test executed because condition is true");
    }

    static boolean customCondition() {
        // Custom logic for enabling the test
        // For example, enable test only if system property 'runCustomTest' is 'true'
        return "true".equals(System.getProperty("runCustomTest"));
    }
}

The test method testRunsOnlyIfConditionTrue is annotated with @EnabledIf("customCondition"). This means JUnit will call the static method customCondition() before running the test.

If customCondition() returns true, the test runs and asserts true to confirm execution.

If it returns false, JUnit skips the test.

The condition method checks a system property runCustomTest. This allows controlling test execution externally, like from command line or build scripts.

This approach keeps tests clean and allows flexible enabling/disabling based on custom logic.

Common Mistakes - 4 Pitfalls

Using non-static methods for @EnabledIf condition

Putting complex logic or side effects inside the condition method

Not referencing the condition method name correctly in @EnabledIf

Using @EnabledIf on non-test methods

Bonus Challenge

Now add data-driven testing with @EnabledIf so that each test case runs only if a custom condition for that data is true

Show Hint