Why @ExtendWith annotation in JUnit? - Purpose & Use Cases

The Big Idea

What if you could add powerful test features with just one simple annotation?

The Scenario

Imagine you have many test classes in JUnit, and each needs special setup or behavior like starting a database, mocking services, or handling test lifecycle events. You try to add this setup code manually inside every test method or class.

The Problem

Manually repeating setup code is slow and boring. You might forget to add it in some tests, causing inconsistent results. It's easy to make mistakes, and your test code becomes messy and hard to maintain.

The Solution

The @ExtendWith annotation lets you plug in reusable extensions that automatically add behaviors to your tests. This keeps your test code clean and consistent, and you write the setup logic only once.

Before vs After

✗ Before

public class MyTest {
  @BeforeEach
  void setup() {
    // start database
    // initialize mocks
  }
  @Test
  void testSomething() { ... }
}

✓ After

@ExtendWith(MyCustomExtension.class)
public class MyTest {
  @Test
  void testSomething() { ... }
}

What It Enables

You can easily add powerful, reusable behaviors to tests, making them cleaner, faster to write, and more reliable.

Real Life Example

For example, you can create an extension that starts a temporary database before tests and stops it after. Using @ExtendWith, all tests needing the database get this setup automatically without repeating code.

Key Takeaways

Manual setup in tests is repetitive and error-prone.

@ExtendWith adds reusable behaviors cleanly.

It improves test reliability and maintainability.