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.