@Disabled for skipping tests in JUnit - Test Execution Trace

Test Overview

This test demonstrates how to use the @Disabled annotation in JUnit to skip a test method. The test verifies that a simple addition operation works correctly, but the test is skipped during execution.

Test Code - JUnit

JUnit

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

public class CalculatorTest {

    @Test
    @Disabled("Skipping this test temporarily")
    void testAddition() {
        int result = 2 + 3;
        assertEquals(5, result, "2 + 3 should equal 5");
    }
}

Execution Trace - 3 Steps

Step	Action	System State	Assertion	Result
1	Test runner discovers testAddition method annotated with @Test and @Disabled	Test suite loaded with one test method marked as disabled	-	PASS
2	Test runner skips execution of testAddition due to @Disabled annotation	No browser or UI involved; test framework skips test execution	No assertions executed because test is skipped	PASS
3	Test report marks testAddition as skipped	Test report shows one skipped test	Skipped test is correctly reported	PASS

Failure Scenario

Failing Condition: Test is not skipped because @Disabled annotation is missing or misspelled

Execution Trace Quiz - 3 Questions

What does the @Disabled annotation do in this JUnit test?

A Skips the test method during execution

B Runs the test method twice

C Marks the test as failed

D Automatically fixes test errors

Key Result

Using @Disabled allows you to temporarily skip tests without deleting code, helping manage test suites during development or debugging.