CtrlK
BlogDocsLog inGet started
Tessl Logo

323-frameworks-spring-boot-testing-acceptance-tests

Use when you need to implement acceptance tests from a Gherkin .feature file for Spring Boot applications — including finding scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Requires .feature file in context. This should trigger for requests such as Review Java code for Spring Boot acceptance tests; Apply best practices for Spring Boot acceptance tests in Java code. Part of cursor-rules-java project

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized, concise, and uses progressive disclosure effectively with clear validation checkpoints. Its only gap is the absence of inline executable code examples, which are instead deferred to the reference.

Suggestions

Include one short inline code snippet (e.g., a minimal BaseAcceptanceTest skeleton or a @SpringBootTest + @ServiceConnection example) so the skill body is actionable without opening the reference.

Show the concrete Surefire/Failsafe *AT include pattern inline, since naming convention is a key actionable detail currently only in the reference.

Add an explicit retry/feedback step in the Workflow (e.g., 'If verify fails, fix and re-run mvn clean verify') to make the validation loop fully self-contained.

DimensionReasoningScore

Conciseness

The body is lean — organized into tight bullet lists and short constraint lines with no padding or explanation of concepts Claude already knows, and it defers detail to the reference with 'Use the reference for detailed examples and constraints'.

3 / 3

Actionability

It provides concrete commands ('./mvnw compile', './mvnw clean verify') and specific annotations (@ServiceConnection, @DynamicPropertySource), but the SKILL.md body itself contains no executable code examples — all code is deferred to the reference, so it is not copy-paste ready on its own.

2 / 3

Workflow Clarity

The 4-step Workflow is clearly sequenced with explicit validation checkpoints — MANDATORY compile before changes, SAFETY stop on failure, and VERIFY with 'mvn clean verify' after — forming a validate/fix/retry feedback loop.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview pointing one level deep to the verified reference file references/323-frameworks-spring-boot-testing-acceptance-tests.md, with clearly signaled navigation in the Reference section.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, trigger-rich, and clearly distinguishes the skill's scope and preconditions. It explicitly answers both what the skill does and when it should be used.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'finding scenarios tagged @acceptance', 'implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs'.

3 / 3

Completeness

Clearly answers both what it does (implement acceptance tests from Gherkin) and when to use it ('Use when you need to implement...') with an explicit 'Requires .feature file in context' precondition.

3 / 3

Trigger Term Quality

Includes natural phrasing a user would say — 'acceptance tests', 'Gherkin .feature file', 'Spring Boot', and explicit trigger requests 'Review Java code for Spring Boot acceptance tests' and 'Apply best practices for Spring Boot acceptance tests in Java code'.

3 / 3

Distinctiveness Conflict Risk

Narrowly scoped to Spring Boot acceptance tests from Gherkin feature files, with explicit redirection to a framework-agnostic sibling skill, making conflicts with other skills unlikely.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.