QA Junit5 Writer

QA JUnit 5 Writer

Purpose

Write JUnit 5 unit and integration tests from test case specifications. Transform structured test cases into executable JUnit 5 test classes with parameterized tests, nested classes for organization, extensions, Mockito mocking, and AssertJ assertions.

Trigger Phrases

• "Write JUnit 5 tests for [class/feature]"
• "Generate unit tests with JUnit 5"
• "Create parameterized tests for [method]"
• "Add JUnit 5 tests with Mockito"
• "JUnit 5 tests with AssertJ assertions"
• "Nested test classes for [feature]"
• "JUnit 5 @ParameterizedTest for [scenarios]"
• "Mockito mocks in JUnit 5 tests"
• "Heal my failing JUnit 5 tests"

Key Features

Workflow

1. Read test cases — From specs, requirements, or manual test designs
2. Analyze Java code — Inspect classes, methods, dependencies
3. Generate test classes — Produce {Class}Test.java with appropriate structure
4. Add mocks/fixtures — Use Mockito for dependencies; fixtures for test data
5. Run — User runs mvn test or ./gradlew test

Key Patterns

Parameterized Tests

@ParameterizedTest
@CsvSource({"admin, true", "user, false"})
void shouldCheckAccess(String role, boolean expected) {
    assertThat(service.hasAccess(role)).isEqualTo(expected);
}

@ParameterizedTest
@MethodSource("provideInvalidInputs")
void shouldRejectInvalidInput(String input) {
    assertThatThrownBy(() -> validator.validate(input))
        .isInstanceOf(ValidationException.class);
}

Nested Classes

Use @Nested for logical grouping; each nested class gets its own @BeforeEach:

@DisplayName("UserService")
class UserServiceTest {
    @Nested
    @DisplayName("when user exists")
    class WhenUserExists {
        @Test
        void shouldReturnUser() { ... }
    }
    @Nested
    @DisplayName("when user not found")
    class WhenUserNotFound {
        @Test
        void shouldThrowException() { ... }
    }
}

File Naming

• {Class}Test.java — Test classes (e.g., UserServiceTest.java, OrderValidatorTest.java)
• Place in src/test/java mirroring production package structure

Scope

Can do (autonomous):

• Generate JUnit 5 unit and integration tests from test case specs
• Use @ParameterizedTest for data-driven scenarios
• Apply @Nested for logical grouping
• Use Mockito for mocking dependencies
• Use AssertJ for fluent assertions
• Add @Tag, @DisplayName for organization
• Configure @TestInstance when shared setup needed
• Use Context7 MCP for JUnit 5/Mockito docs
• Delegate to qa-test-healer when tests fail (Heal Mode)

Cannot do (requires confirmation):

• Change production code structure
• Add dependencies not in pom.xml/build.gradle
• Override project JUnit/Mockito config without approval

Will not do (out of scope):

• Execute tests (user runs mvn test)
• Write Spring integration tests (use qa-spring-test-writer)
• Modify CI/CD pipelines

References

• references/patterns.md — Parameterized, nested, extensions, lifecycle
• references/assertions.md — AssertJ assertion reference
• references/config.md — Maven/Gradle JUnit 5 config, Surefire plugin

Quality Checklist

• @DisplayName used for readability
• @ParameterizedTest for multiple inputs; avoid duplicate test methods
• @Nested for logical grouping where beneficial
• Mockito used for external dependencies; avoid over-mocking
• AssertJ used for assertions
• Tests independent (no shared mutable state)
• One assertion focus per test where practical
• Traceability to test case IDs where applicable
• File naming follows {Class}Test.java convention

Troubleshooting