assertAll for grouped assertions in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of grouped assertions with assertAll

What is the test execution result of the following JUnit code snippet using assertAll?

JUnit

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

class SampleTest {
    @Test
    void testGroupedAssertions() {
        assertAll("group",
            () -> assertEquals(2, 1 + 1),
            () -> assertTrue(3 > 2),
            () -> assertFalse(5 < 3)
        );
    }
}

A Test fails immediately at the first failed assertion inside assertAll.

B Test throws a runtime exception due to incorrect assertAll usage.

C Test fails but only reports the first failed assertion, ignoring others.

D Test passes with all assertions checked and no failures.

💡 Hint

assertAll runs all assertions and reports all failures together.

The assertAll method runs all grouped assertions and reports any failures together after executing all. Since all assertions are true here, the test passes.

❓ assertion

intermediate

Which assertion failure messages are reported by assertAll?

Given the following JUnit test, which assertion failure messages will be reported after running assertAll?

JUnit

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

class SampleTest {
    @Test
    void testFailures() {
        assertAll("failures",
            () -> assertEquals(5, 2 + 2, "Sum mismatch"),
            () -> assertTrue(1 > 2, "Condition failed"),
            () -> assertFalse(false, "Boolean check")
        );
    }
}

A Reports all three failure messages: "Sum mismatch", "Condition failed", and "Boolean check".

B Reports failure: "Boolean check" only.

C Reports failures: "Sum mismatch" and "Condition failed" only.

D No failures reported; test passes.

💡 Hint

Check which assertions actually fail.

The first two assertions fail and their messages are reported. The third assertion assertFalse(false) passes, so its message is not reported.

🔧 Debug

advanced

Identify the error in assertAll usage

What error will occur when running this JUnit test with incorrect assertAll usage?

JUnit

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

class SampleTest {
    @Test
    void testIncorrectAssertAll() {
        assertAll("group",
            assertEquals(1, 1),
            () -> assertTrue(true)
        );
    }
}

A Compilation error: incompatible types, expected Executable but found void.

B Test fails at runtime with AssertionError.

C Test passes successfully without errors.

D NullPointerException at runtime.

💡 Hint

Check the lambda expressions passed to assertAll.

The first argument inside assertAll must be a lambda (Executable). Here, assertEquals(1, 1) is called immediately, returning void, causing a compilation error.

❓ framework

advanced

Best practice for grouping assertions in JUnit 5

Which of the following is the best practice for grouping multiple assertions in JUnit 5 to ensure all assertions run and failures are reported together?

A Use multiple separate assertions without assertAll; test stops at first failure.

B Use assertAll with lambda expressions for each assertion inside a single group.

C Use try-catch blocks around each assertion to catch failures manually.

D Use a custom loop to run assertions and collect failures manually.

💡 Hint

assertAll is designed for grouped assertions.

Using assertAll with lambdas is the recommended way to group assertions so all run and failures are reported together.

🧠 Conceptual

expert

Why use assertAll instead of multiple separate assertions?

What is the main advantage of using assertAll for grouped assertions in JUnit 5 compared to writing multiple separate assertions?

A assertAll runs all assertions and reports all failures together, improving test feedback.

B assertAll runs assertions sequentially but stops at the first failure to save time.

C assertAll automatically retries failed assertions to reduce flaky tests.

D assertAll converts all assertions into warnings instead of failures.

💡 Hint

Think about how test failures are reported.

The key benefit of assertAll is that it executes all assertions and reports all failures at once, giving better feedback than stopping at the first failure.