CUI Java unit testing standards and patterns with JUnit 5, generators, and value object testing
CUI Java unit testing standards and patterns with JUnit 5, generators, and value object testing
npx skills add https://github.com/cuioss/cui-llm-rules --skill cui-java-unit-testing이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
| name | cui-java-unit-testing |
| description | CUI Java unit testing standards and patterns with JUnit 5, generators, and value object testing |
| allowed-tools | ["Read","Edit","Write","Bash","Grep","Glob"] |
Standards and patterns for writing high-quality unit tests in CUI Java projects using JUnit 5, the CUI test generator framework, and value object contract testing.
CRITICAL: Load current testing standards to use as enforcement criteria.
Always load foundational testing standards:
Read: standards/testing-junit-core.md
This provides core JUnit 5 patterns, AAA structure, assertion standards, and test organization that are always needed for testing.
Conditional loading based on testing context:
A. If project uses test data generators (presence of de.cuioss.test.generator imports or @EnableGeneratorController):
Read: standards/test-generator-framework.md
Provides comprehensive generator standards including mandatory requirements, all parameterized testing annotations (@GeneratorsSource, @CompositeTypeGeneratorSource, etc.), seed restrictions, anti-patterns, and complete API reference.
B. If testing value objects (classes with equals/hashCode/toString or annotated with @Value, @Data):
Read: standards/testing-value-objects.md
Provides comprehensive contract testing standards using ShouldHandleObjectContracts<T> interface and proper generator integration.
C. If testing HTTP clients or APIs (testing code that makes HTTP requests):
Read: standards/testing-mockwebserver.md
Provides MockWebServer setup patterns, response mocking, request verification, retry logic testing, and HTTP status code handling.
D. If writing integration tests (tests that interact with multiple components or external systems):
Read: standards/integration-testing.md
Covers Maven surefire/failsafe configuration, integration test naming conventions (*IT.java), profile setup, and CI/CD integration.
E. If testing applications that use Java Util Logging (JUL) (testing code that uses java.util.logging or needs to assert log output):
Read: standards/testing-juli-logger.md
Provides patterns for configuring test loggers with @EnableTestLogger, asserting log statements with LogAsserts, and dynamically changing log levels in tests.
F. If focusing on test quality or reviewing existing tests (improving test quality, eliminating AI-generated artifacts, or ensuring compliance):
Read: standards/testing-quality-standards.md
Provides quality best practices including AI-generated code detection, parameterized test guidelines, assertion message standards, SonarQube compliance, library migration guidelines, and coverage requirements.
Extract key requirements from all loaded standards
Store in working memory for use during task execution
If working with existing tests:
Identify current test structure:
Assess CUI framework compliance:
@EnableGeneratorController usage where neededReview test quality:
When writing or modifying tests:
Apply core JUnit 5 standards:
Use CUI test generator for all data (if applicable):
Implement value object contract testing (if applicable):
Configure HTTP mocking (if applicable):
Set up integration tests (if applicable):
Before completing the task:
Verify standards compliance:
Verify CUI framework usage (if applicable):
Run tests and verify success:
# Run unit tests
Task:
subagent_type: maven-builder
description: Run unit tests
prompt: |
Execute unit tests only.
Parameters:
- command: clean test
CRITICAL: Wait for tests to complete. Inspect results and fix any failures.
# Run integration tests (if applicable)
Task:
subagent_type: maven-builder
description: Run integration tests
prompt: |
Execute integration tests with the integration-tests profile.
Parameters:
- command: clean verify -Pintegration-tests
CRITICAL: Wait for tests to complete. Inspect results and fix any failures.
# Verify coverage
Task:
subagent_type: maven-builder
description: Verify test coverage
prompt: |
Execute tests with coverage analysis using the coverage profile.
Parameters:
- command: clean verify -Pcoverage
CRITICAL: Wait for build to complete. Inspect coverage results and ensure
minimum 80% line/branch coverage is met. Address any coverage gaps.
Check coverage requirements:
Provide summary of:
@EnableGeneratorController
@DisplayName("Token Validator Tests")
class TokenValidatorTest {
@Test
@DisplayName("Should validate token with correct issuer")
void shouldValidateTokenWithCorrectIssuer() {
// Arrange
String issuer = Generators.strings().next();
Token token = createTokenWithIssuer(issuer);
TokenValidator validator = new TokenValidator(issuer);
// Act
ValidationResult result = validator.validate(token);
// Assert
assertTrue(result.isValid(), "Token with correct issuer should be valid");
}
}
@EnableGeneratorController
class UserDataTest implements ShouldHandleObjectContracts<UserData> {
@Override
public UserData getUnderTest() {
return UserData.builder()
.username(Generators.strings().next())
.email(Generators.emailAddress().next())
.age(Generators.integers(18, 100).next())
.build();
}
}
@EnableGeneratorController
class ParameterizedValidationTest {
@ParameterizedTest
@DisplayName("Should validate various email formats")
@GeneratorsSource(generator = GeneratorType.DOMAIN_EMAIL, count = 5)
void shouldValidateEmailFormats(String email) {
assertTrue(validator.isValidEmail(email),
"Generated email should be valid");
}
}
@EnableMockWebServer
@EnableGeneratorController
class HttpClientTest {
@InjectMockWebServer
private MockWebServerHolder serverHolder;
@Test
@DisplayName("Should successfully fetch user data")
void shouldFetchUserData() throws Exception {
// Arrange
String userName = Generators.strings().next();
serverHolder.enqueue(new MockResponse()
.setResponseCode(200)
.setBody(String.format("{\"name\": \"%s\"}", userName)));
// Act
User user = client.getUser(serverHolder.getBaseUrl(), 1);
// Assert
assertNotNull(user, "Response should not be null");
assertEquals(userName, user.getName(), "User name should match");
}
}
If encountering issues:
General documentation standards for README, AsciiDoc, and technical documentation
CDI and Quarkus development standards for CUI projects, including CDI aspects, container configuration, testing, and native optimization
Modern CSS standards covering essentials, responsive design, quality practices, and tooling for CUI projects
Cypress E2E testing standards including framework adaptations, test organization, and best practices
ESLint, Prettier, and StyleLint configuration standards for JavaScript code quality and formatting, including flat config setup, rule management, and build integration
JavaScript project structure, package.json configuration, dependency management, and Maven integration standards for consistent project setup and builds