Why assertions verify expected outcomes in JUnit - Challenge Your Understanding

Challenge - 5 Problems

❓ assertion

intermediate

Understanding assertion failure in JUnit

What will happen when this JUnit assertion runs if the actual value is 5 but the expected value is 10?

JUnit

import static org.junit.jupiter.api.Assertions.assertEquals;

int expected = 10;
int actual = 5;
assertEquals(expected, actual);

A The test throws a NullPointerException because values are not objects.

B The test passes because actual and expected are both integers.

C The test fails with an AssertionError because actual does not equal expected.

D The test is skipped because assertEquals is not called inside a test method.

💡 Hint

Assertions check if actual and expected values match exactly.

Assertions in JUnit compare expected and actual values. If they differ, the test fails with an AssertionError. Here, 5 is not equal to 10, so the assertion fails.

🧠 Conceptual

intermediate

Purpose of assertions in test cases

Why do we use assertions in software tests like JUnit tests?

A To make the program run faster by skipping code.

B To automatically check if the program behaves as expected and report failures.

C To document the code without affecting test results.

D To replace manual testing by users completely.

💡 Hint

Think about what happens when an assertion fails during a test.

Assertions verify that the program's output matches what we expect. If not, they cause the test to fail, helping us find bugs early.

❓ Predict Output

advanced

Output of a failing JUnit assertion with message

What is the output when this JUnit assertion fails?

JUnit

import static org.junit.jupiter.api.Assertions.assertEquals;

String expected = "hello";
String actual = "world";
assertEquals(expected, actual, "Strings do not match!");

A Test fails with AssertionError and message: Strings do not match!

B Test throws compilation error due to wrong assertEquals usage.

C Test passes silently with no output.

D Test fails with NullPointerException because strings differ.

💡 Hint

Check how assertEquals behaves when expected and actual differ and a message is provided.

When assertEquals fails, it throws an AssertionError showing the provided message to explain the failure.

🔧 Debug

advanced

Identify why this assertion does not verify correctly

Why does this assertion fail even though the lists contain the same elements?

JUnit

import java.util.List;
import java.util.ArrayList;
import static org.junit.jupiter.api.Assertions.assertEquals;

List<String> expected = List.of("apple", "banana");
List<String> actual = new ArrayList<>();
actual.add("banana");
actual.add("apple");
assertEquals(expected, actual);

A The assertion fails because the lists have different order of elements.

B The assertion passes because both lists contain the same elements in different order, but List.equals requires order to match.

C The assertion fails because actual is mutable and expected is immutable.

D The assertion passes because List.equals checks only size, not order or content.

💡 Hint

Remember how List.equals works in Java regarding order.

List.equals returns true only if both lists have the same elements in the same order. Here, order differs, so assertion fails.

❓ framework

expert

How does JUnit handle assertion failures during test execution?

When a JUnit assertion fails inside a test method, what does the framework do next?

A JUnit ignores the failure and continues running the rest of the test method.

B JUnit stops all tests in the suite and exits immediately.

C JUnit retries the assertion automatically until it passes or times out.

D JUnit stops executing the current test method immediately and marks it as failed.

💡 Hint

Think about what happens when an exception is thrown inside a test method.

When an assertion fails, it throws an AssertionError which stops the current test method execution and marks it as failed. Other tests continue normally.