423-frameworks-quarkus-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires the .feature file in context. Part of the skills-for-java project
71
63%
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/423-frameworks-quarkus-testing-acceptance-tests/SKILL.mdQuality
Discovery
85%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, highly specific skill description that clearly defines its scope for Quarkus acceptance testing with a detailed technology stack. The explicit 'Use when' clause and specific technical requirements make it easy for Claude to identify when to use this skill. The main weakness is the heavy reliance on technical jargon without including more natural user language variations.
Suggestions
Add natural language trigger terms that users might say, such as 'BDD tests', 'cucumber tests', 'behavior-driven tests', or 'write acceptance tests'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implement acceptance tests from Gherkin files, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager, Testcontainers, WireMock, REST Assured for HTTP testing, WireMock JSON mapping files, *AT suffix naming, and Maven Surefire/Failsafe three-tier split. | 3 / 3 |
Completeness | Clearly answers both what (implement acceptance tests with specific technologies) and when ('Use when you need to implement acceptance tests from a Gherkin .feature file for Quarkus applications'). The 'Use when' clause is explicit and at the beginning. | 3 / 3 |
Trigger Term Quality | Contains relevant technical keywords like 'Gherkin', '.feature file', 'Quarkus', 'acceptance tests', 'Testcontainers', 'WireMock', 'REST Assured', but these are highly technical terms. Missing more natural user phrases like 'write tests', 'BDD tests', or 'cucumber tests'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically Quarkus applications, Gherkin .feature files, and a very specific tech stack (Testcontainers, WireMock, REST Assured). Unlikely to conflict with general testing or other framework-specific skills. | 3 / 3 |
Total | 11 / 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 pointer to a reference file rather than providing actionable guidance itself. While it has good structure and clear preconditions/constraints, it lacks any concrete code examples, making it impossible for Claude to implement acceptance tests without reading the external reference. The skill would benefit significantly from including at least one minimal executable example of BaseAcceptanceTest setup and a sample test method.
Suggestions
Add a minimal executable code example showing BaseAcceptanceTest class structure with @QuarkusTest and @QuarkusTestResource annotations
Include a concrete example of a test method with Given/When/Then comments showing REST Assured usage and WireMock verification
Add a sample WireMock JSON mapping file structure to make the skill immediately actionable
Consolidate the redundant precondition statements in the Constraints section (PRECONDITION, MANDATORY, BLOCKING CONDITION all express similar requirements)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., 'What is covered' section largely duplicates the reference pointer, and constraints section repeats preconditions multiple times with different labels like 'PRECONDITION', 'MANDATORY', 'BLOCKING CONDITION'). | 2 / 3 |
Actionability | The skill describes what should be done but provides no concrete code examples, no executable snippets for BaseAcceptanceTest setup, no sample WireMock JSON mappings, and no REST Assured examples. It relies entirely on an external reference file for actual implementation guidance. | 1 / 3 |
Workflow Clarity | The constraints section establishes a clear sequence (compile → generate → verify) with validation checkpoints, but the actual implementation workflow is deferred to the reference file. The skill itself doesn't provide the step-by-step process for creating the tests. | 2 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview with a clear, one-level-deep reference to the detailed guidance file. The 'When to use this skill' section provides good navigation cues for different use cases. | 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
b36efb2
- 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.