132-java-testing-integration-testing
Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs. This should trigger for requests such as Review Java code for integration tests; Apply best practices for integration tests in Java code. Part of cursor-rules-java project
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/132-java-testing-integration-testing/SKILL.mdQuality
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 a strong, well-crafted skill description that excels across all dimensions. It provides highly specific concrete actions, includes natural trigger terms, explicitly addresses both what and when, and occupies a clear niche around Java integration testing with WireMock. The only minor concern is that it's quite long and dense, but the specificity justifies the length.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists numerous specific concrete actions: generating BaseIntegrationTest.java with WireMock, detecting HTTP client infrastructure from import signals, injecting service coordinates via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, and eliminating specific anti-patterns. | 3 / 3 |
Completeness | Clearly answers both 'what' (set up, review, improve Java integration tests with detailed capabilities) and 'when' ('Use when you need to...' at the start, plus explicit trigger examples like 'Review Java code for integration tests' and 'Apply best practices for integration tests in Java code'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'integration tests', 'Java', 'WireMock', 'HTTP stubs', 'best practices for integration tests', 'review Java code'. Also includes specific technical terms like 'Mockito', 'System.setProperty()', and 'bodyFileName' that power users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Java integration tests with WireMock specifically, including very specific patterns like BaseIntegrationTest.java, HTTP client detection from imports, and WireMock JSON mapping files. Unlikely to conflict with general Java testing or other language testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a pointer to a reference document rather than a standalone actionable guide. It lacks any concrete code examples, executable snippets, or specific patterns despite describing a highly code-centric topic (WireMock integration testing). The workflow structure is reasonable but the core content is descriptive rather than instructive, making it difficult for Claude to act on without the reference file.
Suggestions
Add at least one concrete, executable code example showing a minimal BaseIntegrationTest setup with WireMockExtension and @RegisterExtension — this is the core deliverable and should not be entirely delegated to the reference.
Include a concrete anti-pattern example (bad code) paired with the corrected version (good code) directly in the SKILL.md to make the guidance immediately actionable.
Replace the 'What is covered' bullet list with a brief one-line summary and move the detailed topic enumeration into the reference file — the current list consumes tokens without providing actionable guidance.
Break workflow step 3 into sub-steps with specific validation checkpoints (e.g., verify WireMock starts on dynamic port, verify stubs are isolated per test method) to improve workflow clarity for this multi-step process.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat verbose and reads like a table of contents for the reference file rather than actionable content. The skill explains what it covers rather than just doing it, but it's not egregiously padded. | 2 / 3 |
Actionability | The skill contains no executable code, no concrete examples, no copy-paste ready snippets. It describes concepts (BaseIntegrationTest, WireMock setup, stub isolation) but delegates all actual implementation details to a reference file. The workflow steps are high-level directives without specific commands beyond compile/verify. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with a compilation gate and final verification step, which is good. However, step 3 ('Set up resilient integration-test infrastructure') is vague and bundles multiple complex operations without validation checkpoints between them. The compile-first check is a good safety gate but the middle steps lack granularity. | 2 / 3 |
Progressive Disclosure | The skill references a single detailed reference file (references/132-java-testing-integration-testing.md) which is one level deep and clearly signaled. However, since no bundle files were provided, we cannot verify the reference exists. The SKILL.md itself contains too much descriptive content (the bullet list) that is neither actionable overview nor properly delegated detail — it's an awkward middle ground. | 2 / 3 |
Total | 7 / 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
762cb86
- 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.