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.

Practice

1. What is the main reason to use extensions in JUnit tests?

easy

A. To add extra behavior without changing the test code

B. To write test cases faster

C. To replace the JUnit framework

D. To create user interfaces for tests

Solution

1. Step 1: Understand the purpose of extensions

   Extensions allow adding extra behavior like setup or cleanup without modifying test methods.

2. Step 2: Compare options with this purpose

   Only To add extra behavior without changing the test code matches this purpose; others describe unrelated goals.

3. Final Answer:

   To add extra behavior without changing the test code -> Option A

4. Quick Check:

   Extensions add behavior = D [OK]

Hint: Extensions add behavior without changing tests [OK]

Common Mistakes:

• Thinking extensions speed up writing tests
• Confusing extensions with replacing JUnit
• Assuming extensions create UI

2. Which annotation is used to apply an extension to a JUnit test class or method?

easy

A. @TestExtension

B. @UseExtension

C. @ExtendWith

D. @EnableExtension

Solution

1. Step 1: Recall the correct annotation for extensions

   The standard JUnit annotation to apply extensions is @ExtendWith.

2. Step 2: Verify other options

   Other options are not valid JUnit annotations for extensions.

3. Final Answer:

   @ExtendWith -> Option C

4. Quick Check:

   @ExtendWith = C [OK]

Hint: Remember '@ExtendWith' applies extensions [OK]

Common Mistakes:

• Using @TestExtension which does not exist
• Confusing with @UseExtension or @EnableExtension
• Forgetting the '@' symbol

3. Given this code snippet, what will be printed when the test runs?

@ExtendWith(MyExtension.class)
class MyTest {
  @Test
  void testMethod() {
    System.out.println("Test running");
  }
}

Assuming MyExtension prints "Before test" before the test and "After test" after the test.

medium

A. Test running\nBefore test\nAfter test

B. Before test\nTest running\nAfter test

C. After test\nTest running\nBefore test

D. Test running only

Solution

1. Step 1: Understand extension behavior

   MyExtension runs code before and after the test method, printing "Before test" and "After test" respectively.

2. Step 2: Order of output

   Output order is: before test message, test method message, after test message.

3. Final Answer:

   Before test\nTest running\nAfter test -> Option B

4. Quick Check:

   Extension runs before/after test = A [OK]

Hint: Extensions run code before and after tests [OK]

Common Mistakes:

• Assuming extension runs after test only
• Mixing order of printed lines
• Ignoring extension output

4. Identify the error in this JUnit test using an extension:

@ExtendWith(MyExtension.class)
class TestClass {
  @Test
  void test() {
    System.out.println("Running test");
  }

  void helper() {
    System.out.println("Helper method");
  }
}

Why might helper() not be called during test execution?

medium

A. Extension disables helper methods

B. Helper method must be private

C. Helper method must be static

D. Helper method is not annotated with @Test

Solution

1. Step 1: Check method annotations

   Only methods annotated with @Test run as tests; helper() lacks this annotation.

2. Step 2: Understand extension role

   Extensions do not disable helper methods; they only affect test lifecycle.

3. Final Answer:

   Helper method is not annotated with @Test -> Option D

4. Quick Check:

   Missing @Test means no run = B [OK]

Hint: Only @Test methods run automatically [OK]

Common Mistakes:

• Thinking extensions disable helper methods
• Believing helper must be static or private
• Assuming all methods run as tests

5. You want to create a JUnit extension that changes test data before each test runs. Which approach best uses extensions to achieve this?

hard

A. Implement BeforeEachCallback and modify test data in beforeEach()

B. Override the test method and change data inside it

C. Use @Test annotation with parameters to change data

D. Create a separate test class for each data variation

Solution

1. Step 1: Identify extension interface for pre-test actions

   The BeforeEachCallback interface allows running code before each test method.

2. Step 2: Apply this to modify test data

   Modifying test data in beforeEach() method is the correct way to customize data before tests.

3. Final Answer:

   Implement BeforeEachCallback and modify test data in beforeEach() -> Option A

4. Quick Check:

   BeforeEachCallback modifies data before tests = A [OK]

Hint: Use BeforeEachCallback to run code before tests [OK]

Common Mistakes:

• Trying to override test methods directly
• Misusing @Test parameters for data changes
• Creating many classes instead of using extensions