Failure notification setup in JUnit - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

JUnit Failure Notification Behavior

What will be the output when this JUnit test class runs?

JUnit

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

public class NotificationTest {
    @Test
    void testFailureNotification() {
        assertEquals(5, 2 + 2, "Sum should be 5");
    }
}

A Test passes silently

B Test fails with message: 'Sum should be 5'

C Test fails with message: 'expected: <4> but was: <5>'

D Test throws a compilation error

💡 Hint

Check the assertion and the expected vs actual values.

The assertion expects 5 but the actual sum is 4, so the test fails with the provided message.

❓ assertion

intermediate

Correct Assertion for Failure Notification

Which assertion will cause a failure notification if the method getUserCount() returns 10?

JUnit

public int getUserCount() {
    return 10;
}

A assertEquals(5, getUserCount())

B assertEquals(10, getUserCount())

C assertTrue(getUserCount() == 10)

D assertFalse(getUserCount() == 5)

💡 Hint

Failure occurs when expected and actual values differ.

Only option A expects 5 but the method returns 10, causing a failure notification.

❓ framework

advanced

JUnit Failure Notification Listener Setup

Which code snippet correctly sets up a JUnit 5 TestExecutionListener to notify on test failures?

A

public class FailureListener implements TestExecutionListener {
    @Override
    public void executionFinished(TestIdentifier testIdentifier, TestExecutionResult testExecutionResult) {
        if (testExecutionResult.getStatus() == TestExecutionResult.Status.FAILED) {
            System.out.println("Test failed: " + testIdentifier.getDisplayName());
        }
    }
}

B

public class FailureListener implements TestExecutionListener {
    public void onTestFailure(TestIdentifier testIdentifier) {
        System.out.println("Test failed: " + testIdentifier.getDisplayName());
    }
}

C

public class FailureListener implements TestExecutionListener {
    @Override
    public void executionStarted(TestIdentifier testIdentifier) {
        System.out.println("Test started: " + testIdentifier.getDisplayName());
    }
}

D

public class FailureListener {
    public void executionFinished(TestIdentifier testIdentifier, TestExecutionResult testExecutionResult) {
        if (testExecutionResult.getStatus() == TestExecutionResult.Status.SUCCESSFUL) {
            System.out.println("Test failed: " + testIdentifier.getDisplayName());
        }
    }
}

💡 Hint

Look for the correct interface method and failure status check.

Option A correctly overrides executionFinished and checks for FAILED status to notify failure.

🔧 Debug

advanced

Debugging Missing Failure Notification

A JUnit test fails but no failure notification is sent. Which is the most likely cause?

A The assertion uses assertEquals with correct expected and actual values.

B The test method is annotated with @Test.

C The test class extends from a base test class.

D The failure listener is not registered with the test framework.

💡 Hint

Think about how listeners are connected to the test run.

If the listener is not registered, it will not receive failure events to notify.

🧠 Conceptual

expert

Best Practice for Failure Notification in CI Pipelines

Which practice ensures reliable failure notifications in automated CI pipelines?

A Use print statements inside tests to indicate failures.

B Disable failure notifications to reduce noise in CI logs.

C Configure the test framework to output failure details to standard error and integrate with CI notification tools.

D Only run tests locally and manually check results before pushing code.

💡 Hint

Consider automation and integration with CI tools.

Automated failure notifications integrated with CI tools ensure developers are promptly informed.