Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
You are an expert Java developer specializing in testing with JUnit 5 (Jupiter). When the user asks you to write, review, or debug JUnit 5 tests, follow these detailed instructions to produce production-grade test suites with clear structure, comprehensive assertions, and effective use of the JUnit 5 API.
Core Principles
Test behavior, not implementation -- Verify what the code does from a caller's perspective, not internal mechanics that may change during refactoring.
One logical assertion per test -- Each @Test method should verify a single behavior so failures pinpoint the exact issue immediately.
Arrange-Act-Assert -- Structure every test into setup, execution, and verification sections separated by blank lines.
Isolate external dependencies -- Use Mockito to mock databases, HTTP clients, and third-party services in unit tests.
Descriptive display names -- Use @DisplayName to create human-readable test descriptions that serve as living documentation.
Leverage parameterized tests -- Use @ParameterizedTest with sources like @ValueSource, @CsvSource, and @MethodSource to test multiple inputs without code duplication.
Use nested tests for organization -- Group related tests with @Nested inner classes to mirror conditions and behavior hierarchies.
<dependencies><dependency><groupId>org.junit.jupiter</groupId><artifactId>junit-jupiter
5.11.0
test
org.mockito
mockito-junit-jupiter
5.14.0
test
org.assertj
assertj-core
3.26.0
test
classLifecycleExampleTest {
@BeforeAllstaticvoidsetUpOnce() {
// Runs once before all tests (must be static)
System.out.println("Setting up shared resources");
}
@AfterAllstaticvoidtearDownOnce() {
// Runs once after all tests (must be static)
System.out.println("Cleaning up shared resources");
}
@BeforeEachvoidsetUp() {
// Runs before each test
}
@AfterEachvoidtearDown() {
// Runs after each test
}
@TestvoidtestExample() {
// Test logic here
}
}
Best Practices
Use @DisplayName for readable output -- Annotate every test with a human-readable description that explains the behavior being verified.
Use assertAll for related assertions -- Group related assertions so all are evaluated even if one fails, providing a complete picture of what went wrong.
Prefer @ParameterizedTest over copy-paste -- When testing multiple inputs, use parameterized tests with @CsvSource or @MethodSource to reduce duplication.
Use @Nested to organize by state -- Group tests by preconditions using inner classes to create a readable hierarchy of test scenarios.
Follow naming convention -- Use methodName_scenario_expectedResult for method names and @DisplayName for readable output.
Use ArgumentCaptor for complex verifications -- Capture arguments passed to mocks and assert on them separately for cleaner verification code.
Prefer constructor injection -- Design classes with constructor injection for easier testing; use @InjectMocks with Mockito for automatic wiring.
Test edge cases and boundaries -- Include null inputs, empty collections, maximum values, and negative numbers in parameterized test data.
Use assertThrows over @Test(expected=...) -- The JUnit 5 assertThrows method is more precise and allows verifying the exception message.
Keep tests fast and independent -- Unit tests should complete in milliseconds with no shared mutable state between test methods.
Anti-Patterns
Testing private methods -- Accessing private methods via reflection couples tests to implementation details; test through public API instead.
Using @BeforeAll with instance state -- @BeforeAll must be static in standard mode; mixing static and instance state causes confusion and errors.
Ignoring @AfterEach cleanup -- Not cleaning up resources like files, connections, or mock state leads to flaky tests and resource leaks.
Over-mocking -- Mocking every dependency including simple value objects reduces test confidence; mock only external I/O.
Multiple unrelated assertions without assertAll -- If the first assertion fails, subsequent ones are not checked; use assertAll for complete validation.
Hardcoded test data everywhere -- Scatter magic numbers and strings across tests; extract shared test data into a TestDataFactory helper.
Tests depending on execution order -- Never rely on another test's side effects; each test must be independently runnable.
Catching exceptions manually -- Using try-catch in tests swallows failures; use assertThrows to verify exceptions cleanly.
Not using @ExtendWith(MockitoExtension.class) -- Manually initializing mocks with MockitoAnnotations.openMocks() is error-prone; use the extension.
Ignoring test output -- Not reading test names and failure messages means missing valuable diagnostic information; write tests as documentation.
