assumeTrue and assumeFalse in JUnit - Build an Automation Script

Use assumeTrue and assumeFalse to conditionally run tests

Preconditions (2)

Step 1: Write a test method that uses assumeTrue with a condition that is true

Step 2: Inside the test method, add an assertion that always passes

Step 3: Write another test method that uses assumeFalse with a condition that is false

Step 4: Inside this second test method, add an assertion that always passes

Step 5: Run the tests

✅ Expected Result: Both tests run and pass because the assumptions hold true

Automation Requirements - JUnit 5

Assertions Needed:

assertTrue for a simple true condition

assertEquals for verifying expected values

Best Practices:

Use assumeTrue and assumeFalse to skip tests when preconditions are not met

Keep assumptions simple and clear

Use descriptive messages in assumptions for clarity

Automated Solution

JUnit

import static org.junit.jupiter.api.Assumptions.assumeTrue;
import static org.junit.jupiter.api.Assumptions.assumeFalse;
import static org.junit.jupiter.api.Assertions.assertTrue;
import static org.junit.jupiter.api.Assertions.assertEquals;

import org.junit.jupiter.api.Test;

public class AssumptionsTest {

    @Test
    void testWithAssumeTrue() {
        assumeTrue(5 > 1, "Assumption failed: 5 is not greater than 1");
        // This assertion runs only if assumption is true
        assertTrue(3 < 4, "3 should be less than 4");
    }

    @Test
    void testWithAssumeFalse() {
        assumeFalse(2 > 3, "Assumption failed: 2 is greater than 3");
        // This assertion runs only if assumption is false
        assertEquals(10, 5 + 5, "5 + 5 should equal 10");
    }
}

The code imports assumeTrue and assumeFalse from JUnit 5 to conditionally run tests.

In testWithAssumeTrue, the assumption 5 > 1 is true, so the test continues and the assertion 3 < 4 passes.

In testWithAssumeFalse, the assumption 2 > 3 is false, so assumeFalse passes and the test runs the assertion 5 + 5 == 10.

If an assumption fails, the test is skipped, not failed. This helps when tests depend on certain conditions.

Common Mistakes - 3 Pitfalls

Using assumetrue with a false condition expecting the test to fail

Not providing a message in assumetrue or assumefalse

Using assumetrue or assumefalse inside assertions or after assertions

Bonus Challenge

Now add data-driven testing with 3 different conditions using assumeTrue and assumeFalse

Show Hint