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. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
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 an excellent skill description that clearly articulates specific capabilities, includes natural trigger terms developers would use, and explicitly states when to use it. The description is comprehensive yet focused on a distinct technical niche (Java integration testing with WireMock), making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generating a BaseIntegrationTest.java with WireMock', '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', and 'eliminating anti-patterns'. | 3 / 3 |
Completeness | Explicitly answers both what (detailed list of capabilities) and when ('Use when you need to set up, review, or improve Java integration tests') with clear trigger guidance at the start of the description. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Java integration tests', 'WireMock', 'HTTP stubs', 'BaseIntegrationTest', 'HTTP client', 'Mockito', 'stubs'. These are terms developers naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: Java integration tests with WireMock, HTTP stubbing, and specific anti-patterns. Unlikely to conflict with general Java skills or other testing skills due to the precise technical scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%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 table of contents pointing to external reference material rather than providing actionable guidance itself. While it has good structure and appropriate progressive disclosure, it lacks the concrete code examples and executable guidance that would make it immediately useful. The constraints section is well-done with clear validation checkpoints.
Suggestions
Add a minimal executable code example showing BaseIntegrationTest setup with WireMockExtension and @RegisterExtension
Include at least one concrete WireMock stub example (either JSON mapping or programmatic DSL) that can be copy-pasted
Add a brief 'Quick start' section with the essential 3-4 steps to get integration tests running before pointing to the reference
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary listing of concepts (the 'What is covered' bullet list) that could be more concise. The content doesn't over-explain basics but could be tighter. | 2 / 3 |
Actionability | The skill lacks any concrete, executable code examples. It lists concepts and references external documentation but provides no copy-paste ready code for setting up WireMock, creating stubs, or implementing BaseIntegrationTest. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear sequence (compile → apply → verify) with explicit validation checkpoints, but the main workflow for actually implementing integration tests is absent - it just points to a reference file. | 2 / 3 |
Progressive Disclosure | The skill appropriately structures content as an overview with a clear, one-level-deep reference to detailed documentation. The reference link is well-signaled and the organization is logical. | 3 / 3 |
Total | 8 / 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.