Java testing strategies

Java testing strategies

Apply proven testing strategies (RIGHT-BICEP, A-TRIP, CORRECT) to design and verify Java unit tests.

What is covered in this Skill?

• RIGHT-BICEP: Key questions to guide test creation — Right results, Boundary conditions, Inverse relationships, Cross-checks, Error conditions, Performance
• A-TRIP: Characteristics of good tests — Automatic, Thorough, Repeatable, Independent, Professional
• CORRECT: Boundary condition verification — Conformance, Ordering, Range, Reference, Existence, Cardinality, Time

Constraints

Before applying any test strategy changes, ensure the project compiles. If compilation fails, stop immediately — do not proceed until resolved. After applying improvements, run full verification.

• MANDATORY: Run ./mvnw compile or mvn compile before applying any change
• SAFETY: If compilation fails, stop immediately and do not proceed — compilation failure is a blocking condition
• VERIFY: Run ./mvnw clean verify or mvn clean verify after applying improvements
• BEFORE APPLYING: Read only the testing-strategy references selected by the user's concern before changing tests
• FOCUSED ROUTING: For missing behavior coverage or RIGHT-BICEP requests, read references/130-java-testing-strategies-right-bicep.md by default
• FOCUSED ROUTING: For flaky, brittle, manual, order-dependent, shared-state, or maintainability requests, read references/130-java-testing-strategies-a-trip.md by default
• FOCUSED ROUTING: For boundary-condition or CORRECT requests, read references/130-java-testing-strategies-correct.md by default
• BROAD REVIEW: For broad test-strategy reviews, combine RIGHT-BICEP, A-TRIP, and CORRECT references and categorize findings by technique
• EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
• EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
• EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off

When to use this skill

• Review Java code for testing strategies
• Find missing Java test cases or behavior coverage gaps
• Apply RIGHT-BICEP testing strategies in Java code
• Review flaky, brittle, order-dependent, or hard-to-maintain Java tests
• Apply A-TRIP testing strategies in Java code
• Review Java boundary condition tests
• Apply CORRECT boundary condition verification in Java code

Workflow

1. Compile project before test-strategy changes