assumingThat for conditional assertions in JUnit - Build an Automation Script

Use assumingThat to run assertions conditionally in JUnit

Preconditions (2)

Step 1: Create a test method

Step 2: Define a boolean condition (e.g., isWindows = true if OS is Windows)

Step 3: Use assumingThat with the condition and a lambda containing assertions

Step 4: Run the test

Step 5: Verify that assertions inside assumingThat run only if the condition is true

Step 6: Verify that if the condition is false, the assertions inside assumingThat are skipped but the test does not fail

✅ Expected Result: Assertions inside assumingThat run only when the condition is true. If the condition is false, those assertions are skipped without failing the test.

Automation Requirements - JUnit 5

Assertions Needed:

Verify that assumingThat runs assertions only when condition is true

Verify that test passes when condition is false and assertions inside assumingThat are skipped

Best Practices:

Use @Test annotation for test methods

Use org.junit.jupiter.api.Assumptions.assumingThat for conditional assertions

Keep assertions inside lambda passed to assumingThat

Use descriptive assertion messages

Avoid side effects inside assumingThat lambda

Automated Solution

JUnit

import static org.junit.jupiter.api.Assumptions.assumingThat;
import static org.junit.jupiter.api.Assertions.assertEquals;
import org.junit.jupiter.api.Test;

public class ConditionalAssertionTest {

    @Test
    void testConditionalAssertion() {
        boolean isWindows = System.getProperty("os.name").toLowerCase().contains("win");

        assumingThat(isWindows, () -> {
            // This assertion runs only if isWindows is true
            assertEquals("windows 10", System.getProperty("os.name").toLowerCase(), "OS name should be windows 10");
        });

        // This assertion always runs
        assertEquals(5, 2 + 3, "Basic math should work");
    }
}

This test method testConditionalAssertion uses assumingThat to run an assertion only if the isWindows condition is true. The condition checks if the OS name contains "win" (case-insensitive).

If the condition is true, the assertion inside the lambda verifies the OS name equals "windows 10" (lowercase). If false, this assertion is skipped without failing the test.

The second assertion assertEquals(5, 2 + 3) runs always to show the test continues normally.

This approach helps run assertions only when relevant, avoiding false failures on other platforms.

Common Mistakes - 3 Pitfalls

Using assumingThat without a lambda expression

{'mistake': 'Putting side effects or state changes inside assumingThat lambda', 'why_bad': "If the condition is false, the lambda is skipped, so side effects won't run, causing inconsistent test behavior.", 'correct_approach': 'Keep only assertions inside assumingThat lambda; do side effects outside to ensure consistent test setup.'}

Using assumingThat for test setup instead of assertions

Bonus Challenge

Now add data-driven testing with 3 different OS names to verify assumingThat behavior

Show Hint