Why assumptions control test execution in JUnit - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How do assumptions affect test execution flow?

In JUnit, what happens when an assumption fails during test execution?

A The test is skipped and marked as ignored without failing.

B The test fails immediately with an assertion error.

C The test continues running but logs a warning.

D The test is retried automatically until the assumption passes.

💡 Hint

Think about what assumptions are used for in conditional test execution.

When an assumption fails, JUnit skips the test instead of failing it. This helps avoid false failures when preconditions are not met.

❓ Predict Output

intermediate

Output of test with failed assumption

What is the test result when the following JUnit test runs?

JUnit

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

public class SampleTest {
    @Test
    void testOnlyOnWindows() {
        assumeTrue(System.getProperty("os.name").startsWith("Windows"));
        // test code here
    }
}

A Test passes regardless of OS.

B Test fails with AssertionError if OS is not Windows.

C Test is skipped if OS is not Windows.

D Test throws NullPointerException if OS property is missing.

💡 Hint

Check what assumeTrue does when the condition is false.

The assumeTrue method skips the test if the condition is false, so on non-Windows OS the test is skipped.

❓ assertion

advanced

Correct use of assumptions in JUnit

Which code snippet correctly uses assumptions to skip a test when a required environment variable is missing?

A assertTrue(System.getenv("API_KEY") != null, "API_KEY is required");

B assumeTrue(System.getenv("API_KEY") != null, "API_KEY is required");

C assumeFalse(System.getenv("API_KEY") == null, "API_KEY is required");

D assumeThat(System.getenv("API_KEY"), is(notNullValue()));

💡 Hint

Remember assumptions skip tests when conditions are false.

assumeTrue skips the test if the condition is false. Option B correctly skips when API_KEY is missing.

🔧 Debug

advanced

Why does this assumption not skip the test?

Given the code below, why does the test fail instead of skipping when the assumption is false?

JUnit

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

public class DebugTest {
    @Test
    void test() {
        if (!System.getProperty("user.name").equals("admin")) {
            assumeTrue(false, "Only admin can run this test");
        }
        assertTrue(true);
    }
}

A The assumption is inside an if block that never runs, so it does not skip.

B The test fails because assumeTrue is called with false inside an if, causing an error.

C assumeTrue(false) always fails the test instead of skipping.

D The test fails because the assumption is not called unconditionally and the condition logic is wrong.

💡 Hint

Check the logic of the if condition and when assumeTrue is called.

The if condition is inverted or incorrect, so assumeTrue(false) is not called when expected, causing the test to fail instead of skip.

❓ framework

expert

How assumptions integrate with JUnit 5 test lifecycle

Which statement best describes how assumptions affect the execution of lifecycle methods (@BeforeEach, @AfterEach) in JUnit 5?

A If an assumption fails in @BeforeEach, the test and @AfterEach are skipped.

B If an assumption fails in @BeforeEach, the test is skipped but @AfterEach still runs.

C Assumptions do not affect lifecycle methods; they only affect test methods.

D If an assumption fails in @AfterEach, the test is marked as failed.

💡 Hint

Consider what happens when setup assumptions fail before the test runs.

If an assumption fails in @BeforeEach, JUnit skips the test and does not run @AfterEach because the test was never executed.