Why extensions customize JUnit behavior - Test Execution Impact

Test Overview

This test checks how a JUnit extension customizes test behavior by adding a setup step before each test and verifying it runs correctly.

Test Code - JUnit 5

JUnit

import org.junit.jupiter.api.extension.BeforeEachCallback;
import org.junit.jupiter.api.extension.ExtensionContext;
import org.junit.jupiter.api.extension.RegisterExtension;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertTrue;

class CustomSetupExtension implements BeforeEachCallback {
    boolean setupDone = false;

    @Override
    public void beforeEach(ExtensionContext context) {
        setupDone = true; // Custom setup logic
    }
}

public class ExtensionBehaviorTest {

    @RegisterExtension
    static CustomSetupExtension extension = new CustomSetupExtension();

    @Test
    void testSetupIsDone() {
        assertTrue(extension.setupDone, "Setup should be done before test");
    }
}

Execution Trace - 4 Steps

Step	Action	System State	Assertion	Result
1	JUnit test runner starts the ExtensionBehaviorTest class	Test class loaded, extension registered	-	PASS
2	JUnit calls beforeEach method of CustomSetupExtension before testSetupIsDone	Extension's setupDone flag set to true	-	PASS
3	JUnit runs testSetupIsDone method	Test method executing with extension.setupDone == true	assertTrue(extension.setupDone) verifies setupDone is true	PASS
4	JUnit completes test and reports result	Test passed successfully	-	PASS

Failure Scenario

Failing Condition: Extension's beforeEach method does not run or does not set setupDone to true

Execution Trace Quiz - 3 Questions

What does the CustomSetupExtension do before each test?

A Sets a flag indicating setup is done

B Skips the test execution

C Changes the test method name

D Throws an exception

Key Result

JUnit extensions customize test behavior by hooking into lifecycle events like beforeEach, allowing reusable setup or teardown logic outside test methods.