What problem does it solve? Writing consistent, maintainable unit tests in Java requires knowing JUnit 5 conventions, parameterized test sources, assertion patterns, and mocking setup, which developers often get wrong or apply inconsistently. ## Core Features & Use Cases - Test Structure Guidance: Enforces AAA pattern, naming conventions, lifecycle annotations like @BeforeEach, and @DisplayName usage. - Data-Driven Testing: Covers @ParameterizedTest with @ValueSource, @MethodSource, @CsvSource, @CsvFileSource, and @EnumSource. - Assertions & Mocking: Recommends Assertions static methods, AssertJ fluent assertions, assertThrows, assertAll, and Mockito with @Mock and @InjectMocks. - Use Case: When adding tests for a new Calculator service class, generate a CalculatorTest with parameterized cases for edge inputs and mocked dependencies. ## Quick Start Write JUnit 5 tests for my Calculator class including parameterized tests for the divide method and a Mockito mock for its repository dependency.