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

Practice

1.

What happens when assumeTrue(condition) is used in a JUnit test and the condition is false?

easy

A. The test is skipped and marked as ignored.

B. The test fails with an assertion error.

C. The test passes regardless of the condition.

D. The test runs normally without any effect.

Solution

1. Step 1: Understand assumeTrue behavior

   assumeTrue(condition) runs the test only if the condition is true; otherwise, it skips the test.

2. Step 2: Apply condition false scenario

   If the condition is false, the test is skipped and marked as ignored, not failed.

3. Final Answer:

   The test is skipped and marked as ignored. -> Option A

4. Quick Check:

   assumeTrue(false) skips test [OK]

Hint: assumeTrue skips test if condition is false [OK]

Common Mistakes:

• Thinking assumeTrue fails the test on false condition
• Confusing assumeTrue with assertTrue
• Assuming test runs normally regardless

2.

Which of the following is the correct syntax to skip a test in JUnit if a boolean variable isReady is false?

boolean isReady = false;

easy

A. assumeFalse(isReady);

B. assumeTrue(isReady);

C. assumeTrue(!isReady);

D. assumeFalse(!isReady);

Solution

1. Step 1: Understand the goal

   We want to skip the test if isReady is false, so the test should run only if isReady is true.

2. Step 2: Choose correct assume method

   assumeTrue(isReady); runs the test only if isReady is true; otherwise, it skips the test.

3. Final Answer:

   assumeTrue(isReady); -> Option B

4. Quick Check:

   Skip if false = assumeTrue(true) runs [OK]

Hint: Use assumeTrue(variable) to run only if true [OK]

Common Mistakes:

• Using assumeFalse(isReady) which skips when true
• Negating variable incorrectly
• Confusing assumeTrue and assumeFalse usage

3.

Consider the following JUnit test snippet:

import static org.junit.jupiter.api.Assumptions.*;

@Test
void testFeature() {
    assumeFalse(System.getProperty("os.name").startsWith("Windows"));
    assertTrue(true);
}

What happens when this test runs on a Windows machine?

medium

A. The test runs and passes because the assumption is true.

B. The test fails because the assumption is false.

C. The test is skipped because the assumption is false.

D. The test runs and fails because assertTrue is false.

Solution

1. Step 1: Evaluate the assumption on Windows

   On Windows, System.getProperty("os.name") starts with "Windows", so assumeFalse(true) is called.

2. Step 2: Understand assumeFalse behavior

   assumeFalse(true) causes the test to be skipped, not failed.

3. Final Answer:

   The test is skipped because the assumption is false. -> Option C

4. Quick Check:

   assumeFalse(true) skips test [OK]

Hint: assumeFalse(true) skips test [OK]

Common Mistakes:

• Thinking test fails on failed assumption
• Confusing assumeFalse with assertFalse
• Ignoring OS check effect

4.

Identify the error in the following JUnit test code snippet:

import static org.junit.jupiter.api.Assumptions.*;

@Test
void testExample() {
    assumeTrue();
    assertEquals(5, 2 + 3);
}

medium

A. assertEquals is used incorrectly without expected value.

B. Static import of assumptions is missing.

C. The test method must return a boolean.

D. assumeTrue requires a boolean condition argument.

Solution

1. Step 1: Check assumeTrue usage

   assumeTrue() is called without any argument, but it requires a boolean condition.

2. Step 2: Verify other parts

   assertEquals(5, 2 + 3); is correct; static import is present.

3. Final Answer:

   assumeTrue requires a boolean condition argument. -> Option D

4. Quick Check:

   assumeTrue(condition) needs argument [OK]

Hint: assumeTrue always needs a boolean argument [OK]

Common Mistakes:

• Calling assumeTrue without argument
• Confusing assumeTrue with assertTrue
• Ignoring compiler errors on missing argument

5.

You want to write a JUnit test that only runs on Linux systems and skips on others. Which code snippet correctly uses assumeTrue or assumeFalse to achieve this?

hard

A. assumeTrue(System.getProperty("os.name").startsWith("Linux"));

B. assumeFalse(System.getProperty("os.name").startsWith("Linux"));

C. assumeTrue(!System.getProperty("os.name").startsWith("Linux"));

D. assumeFalse(!System.getProperty("os.name").startsWith("Linux"));

Solution

1. Step 1: Define the condition for Linux

   The test should run only if the OS name starts with "Linux".

2. Step 2: Use assumeTrue with Linux condition

   assumeTrue(System.getProperty("os.name").startsWith("Linux")); runs the test only on Linux, skips otherwise.

3. Final Answer:

   assumeTrue(System.getProperty("os.name").startsWith("Linux")); -> Option A

4. Quick Check:

   Run only if Linux = assumeTrue(Linux) [OK]

Hint: Use assumeTrue with positive condition to run test [OK]

Common Mistakes:

• Using assumeFalse with Linux condition incorrectly
• Negating condition wrongly
• Confusing assumeTrue and assumeFalse logic