assumeTrue and assumeFalse in JUnit - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the JUnit method assumeTrue(condition) do in a test?

It checks if the condition is true. If it is false, the test is skipped (ignored), not failed.

beginner

How does assumeFalse(condition) behave in a JUnit test?

It checks if the condition is false. If the condition is true, the test is skipped (ignored).

intermediate

Why use assumeTrue or assumeFalse instead of assertTrue or assertFalse?

Assumptions skip tests when conditions are not met, useful for environment checks. Assertions fail tests when conditions are not met.

beginner

What happens to a test result if an assumption fails in JUnit?

The test is marked as skipped or ignored, not as failed or passed.

beginner

Give a simple example of using assumeTrue in a JUnit test.

Example:

assumeTrue(System.getProperty("os.name").startsWith("Windows"));
// test code that runs only on Windows

What does assumeTrue(false) do in a JUnit test?

A Fails the test

B Throws an exception

C Skips the test

D Passes the test

If the condition is false, assumeTrue causes the test to be skipped, not failed.

Which method skips a test if the condition is true?

A assumeTrue

B assumeFalse

C assertTrue

D assertFalse

assumeFalse skips the test if the condition is true.

When should you use assumptions in tests?

A To check if test conditions are met before running

B To fail tests on errors

C To log test results

D To assert expected output

Assumptions check if conditions are right to run the test; if not, the test is skipped.

What is the difference between assumeTrue and assertTrue?

A Both skip test if false

B assumeTrue fails test if false; assertTrue skips test if false

C Both fail test if false

D assumeTrue skips test if false; assertTrue fails test if false

assumeTrue skips test when condition is false; assertTrue fails the test.

If an assumption fails, what is the test status?

A Skipped

B Failed

C Passed

D Error

Failing an assumption causes the test to be skipped, not failed.

Explain how assumeTrue and assumeFalse control test execution in JUnit.

Think about when you want to skip tests instead of failing them.

Describe a real-life scenario where using assumeTrue would be helpful in testing.

Imagine you only want to run a test on Windows machines.

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