422-frameworks-quarkus-testing-integration-tests
Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. 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/422-frameworks-quarkus-testing-integration-tests/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 thoroughly covers specific capabilities, includes abundant natural trigger terms, explicitly addresses both what and when, and occupies a clear niche. The only minor weakness is that it's quite verbose and could be slightly more concise, but the detail serves the purpose of disambiguation well. The description follows third-person voice conventions appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: @QuarkusTest, Dev Services, Testcontainers, WireMock stubs, @QuarkusIntegrationTest, REST Assured, data isolation strategies, Maven Surefire/Failsafe split. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (write/improve integration tests with specific technologies and patterns) and 'when' (explicit trigger phrases like 'Add or improve integration tests in a Quarkus project', 'Configure Testcontainers or Dev Services', etc.). The 'This should trigger for requests such as' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'integration tests', 'Quarkus', 'Testcontainers', 'Dev Services', 'WireMock', '@QuarkusIntegrationTest', 'test data isolation', 'Maven Surefire/Failsafe', 'native binary testing'. These are exactly the terms a developer working with Quarkus testing would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Quarkus integration testing specifically, with very specific framework and tool references (@QuarkusTest, Dev Services, WireMock, Testcontainers). Unlikely to conflict with general Java testing skills or other framework-specific 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 table of contents pointing to an external reference file, with almost no actionable content in the SKILL.md itself. While the structure and workflow are reasonable, the complete absence of concrete code examples, specific configuration snippets, or executable patterns for any of the eight advertised topics makes it largely non-actionable on its own. The constraints section is redundant, saying 'compile first' four different ways.
Suggestions
Add at least 2-3 concrete, executable code examples directly in SKILL.md for the most common patterns (e.g., a minimal @QuarkusTest with REST Assured, a Dev Services configuration snippet, a WireMock stub setup via QuarkusTestResourceLifecycleManager).
Consolidate the constraints section — the five bullet points about compilation can be reduced to a single clear directive with a verification step.
Make workflow steps actionable by including specific commands and decision points, e.g., 'If tests use HTTP endpoints, add @BeforeEach cleanup; if tests are repository-level, use @TestTransaction'.
Remove the 'What is covered' bullet list which duplicates the 'When to use' section and the skill description, or replace it with a quick-reference cheat sheet of annotations and their purposes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list largely restates the description and 'When to use' section, creating redundancy. The constraints section is somewhat verbose with multiple synonymous directives (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION all say 'compile first'). However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill contains no executable code, no concrete examples, no specific commands beyond generic './mvnw compile' and './mvnw clean verify'. All actual guidance is deferred to an external reference file. There are no copy-paste ready patterns for @QuarkusTest, Dev Services, WireMock, REST Assured, or any of the advertised topics. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with a verification step at the end, and the constraints section includes a compile-first check. However, the steps are abstract ('Apply framework-aligned changes', 'Gather scope') rather than concrete, and there's no explicit feedback loop for handling test failures or validation errors during the process. | 2 / 3 |
Progressive Disclosure | The skill references a single detailed reference file with a clear path, which is appropriate progressive disclosure structure. However, since no bundle files were provided, we cannot verify the reference exists or assess its quality. The SKILL.md itself is essentially a thin shell that delegates almost everything to the reference, providing too little standalone value in the overview. | 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
ef4eba3
- 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.