131-java-testing-unit-testing
Use when you need to review, improve, or write Java unit tests — including migrating from JUnit 4 to JUnit 5, adopting AssertJ for fluent assertions, structuring tests with Given-When-Then, ensuring test independence, applying parameterized tests, mocking dependencies with Mockito, verifying boundary conditions (RIGHT-BICEP, CORRECT, A-TRIP), leveraging JSpecify null-safety annotations, or eliminating testing anti-patterns such as reflection-based tests or shared mutable state. Part of the skills-for-java project
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that comprehensively covers Java unit testing capabilities with specific frameworks, methodologies, and anti-patterns. It leads with a clear 'Use when' clause and includes numerous natural trigger terms that developers would actually use. The description is distinctive enough to avoid conflicts with other skills while being thorough about its scope.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'migrating from JUnit 4 to JUnit 5', 'adopting AssertJ for fluent assertions', 'structuring tests with Given-When-Then', 'mocking dependencies with Mockito', 'verifying boundary conditions', 'eliminating testing anti-patterns'. Very comprehensive list of specific capabilities. | 3 / 3 |
Completeness | Explicitly answers both what (review, improve, write Java unit tests with specific techniques) AND when ('Use when you need to...'). The 'Use when' clause is present at the start and provides clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Java unit tests', 'JUnit 4', 'JUnit 5', 'AssertJ', 'Given-When-Then', 'parameterized tests', 'Mockito', 'RIGHT-BICEP', 'CORRECT', 'A-TRIP', 'JSpecify', 'reflection-based tests'. These are terms developers naturally use when discussing Java testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Java unit testing specifically, with unique triggers like JUnit versions, AssertJ, Mockito, and testing methodologies (RIGHT-BICEP, CORRECT, A-TRIP). Unlikely to conflict with general coding or other language testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently communicates scope and constraints while properly deferring detailed examples to a reference file. The workflow is clear with explicit validation checkpoints. The main weakness is that the skill itself contains no concrete code examples, relying entirely on the reference file for actionable patterns.
Suggestions
Add 1-2 minimal code examples directly in the skill (e.g., a basic JUnit 5 test structure or AssertJ assertion) to make the skill immediately actionable without requiring reference file access
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing a clear overview without explaining concepts Claude already knows. It lists what's covered without verbose explanations of what JUnit or AssertJ are. | 3 / 3 |
Actionability | The skill provides clear constraints with specific commands (./mvnw compile, mvn clean verify) but lacks concrete code examples in the main file. All detailed examples are deferred to the reference file, making the skill itself more of a pointer than executable guidance. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit validation checkpoints: compile first (blocking condition), apply changes, then verify. The MANDATORY/SAFETY/VERIFY structure makes the sequence unambiguous with clear error recovery guidance. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear scope definition, and a single well-signaled reference to detailed documentation. The content is appropriately split between overview (SKILL.md) and detailed examples (reference file). | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
7772a1b
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.