Why @Nested inner classes in JUnit? - Purpose & Use Cases

The Big Idea

Discover how a simple structure change can turn your chaotic tests into a clear, easy-to-navigate suite!

The Scenario

Imagine testing a complex feature with many related parts by writing all tests in one big class. It becomes a messy list where it's hard to find or understand which tests belong to which part.

The Problem

Manually grouping tests by naming or comments is slow and confusing. You might miss running some tests or misunderstand their purpose. It's like having a cluttered toolbox where you can't find the right tool quickly.

The Solution

@Nested inner classes let you organize tests inside a main test class in smaller, meaningful groups. This makes tests easier to read, maintain, and run in a logical order, just like having labeled drawers for your tools.

Before vs After

✗ Before

class CalculatorTest {
  @Test void addPositive() {}
  @Test void addNegative() {}
  @Test void subtractPositive() {}
  @Test void subtractNegative() {}
}

✓ After

class CalculatorTest {
  @Nested
  class AddTests {
    @Test void positive() {}
    @Test void negative() {}
  }
  @Nested
  class SubtractTests {
    @Test void positive() {}
    @Test void negative() {}
  }
}

What It Enables

It enables clear, logical test structure that mirrors real feature parts, making tests easier to understand and maintain.

Real Life Example

Testing a shopping cart where you group tests for adding items, removing items, and calculating totals separately inside nested classes.

Key Takeaways

Manual test grouping is messy and error-prone.

@Nested classes organize tests into clear, related groups.

This improves readability, maintenance, and test clarity.