421-frameworks-quarkus-testing-unit-tests

Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Quarkus project; Reduce slow @QuarkusTest usage with Mockito-first tests; Add @InjectSpy partial mocking or QuarkusTestProfile configuration in Quarkus tests; Convert repeated test methods to @ParameterizedTest with @CsvSource or @MethodSource; Write fast pure unit tests for Quarkus services. Part of Plinth Toolkit

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

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

A well-structured overview body with a clear validated workflow and clean one-level-deep reference linkage. It loses a little conciseness to repeated compile-gate labels and keeps no inline code examples, relying on the reference for actionability.

Suggestions

Collapse the redundant compile-gate labels in Constraints (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION all restate 'compile first') into a single rule plus the stop-on-failure feedback loop.

Add one short inline good/bad snippet (e.g. a minimal @ExtendWith(MockitoExtension.class) vs. an unnecessary @QuarkusTest) so the body is actionable without opening the reference.

Trim the 'What is covered' bullet list and 'When to use' trigger list, which overlap heavily with the description frontmatter.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude knows Quarkus/Mockito, but the Constraints section restates the 'compile before changes' point across MANDATORY, PREREQUISITE, SAFETY, and BLOCKING CONDITION labels, which is minor padding. Not a 5 because of that repetition; not a 3 because overall it stays efficient.	4 / 5
Actionability	Provides concrete commands (./mvnw compile, mvn clean verify) and specific annotation names to apply, but delegates all executable code examples to the reference file with none inline. Mostly executable guidance with a minor gap, rather than fully copy-paste ready in-body.	4 / 5
Workflow Clarity	A clearly sequenced 4-step workflow (read reference & assess, gather scope, apply changes, verify & report) with explicit validation checkpoints — MANDATORY compile before, VERIFY after, and a feedback loop ('If compilation fails, stop immediately') appropriate for test refactors.	5 / 5
Progressive Disclosure	The body is an overview that points to a single one-level-deep reference (references/421-frameworks-quarkus-testing-unit-tests.md, verified to exist) via a clearly signaled markdown link, with bulk examples correctly offloaded to that file.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that concretely enumerates capabilities, gives explicit 'Use when' guidance with natural trigger phrases, and distinguishes itself from adjacent skills via cross-references. No padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock, @InjectSpy, REST Assured, @ParameterizedTest with @CsvSource/@MethodSource, QuarkusTestProfile, and naming conventions — giving comprehensive coverage rather than vague claims.	5 / 5
Completeness	Explicitly answers both what (write fast unit tests for Quarkus, enumerating the techniques) and when ('Use when you need to write fast unit tests for Quarkus applications' plus a 'This should trigger for requests such as' list of concrete triggers).	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would actually say ('Add or improve unit tests in a Quarkus project', 'Reduce slow @QuarkusTest usage with Mockito-first tests', 'Convert repeated test methods to @ParameterizedTest') alongside the technical annotations, covering common variations.	5 / 5
Distinctiveness Conflict Risk	Clearly niched to Quarkus unit testing and explicitly routes framework-agnostic Java to @131-java-testing-unit-testing, minimizing overlap and conflict with sibling skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/421-frameworks-quarkus-testing-unit-tests/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.