Add Library Test
osama-raddad/FireCrasher
Add or update a Robolectric JVM unit test for the FireCrasher library.
A skill your agent uses when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI…
Install 421 Frameworks Quarkus Testing Unit Tests
$ npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 421-frameworks-quarkus-testing-unit-tests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/421-frameworks-quarkus-testing-unit-tests .claude/skills/421-frameworks-quarkus-testing-unit-tests && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "421-frameworks-quarkus-testing-unit-tests" agent skill from https://github.com/jabrena/plinth/tree/main/skills/421-frameworks-quarkus-testing-unit-tests into .claude/skills/421-frameworks-quarkus-testing-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "421-frameworks-quarkus-testing-unit-tests", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jabrena/plinth/tree/main/skills/421-frameworks-quarkus-testing-unit-testsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 421-frameworks-quarkus-testing-unit-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/421-frameworks-quarkus-testing-unit-tests .agents/skills/421-frameworks-quarkus-testing-unit-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "421-frameworks-quarkus-testing-unit-tests" agent skill from https://github.com/jabrena/plinth/tree/main/skills/421-frameworks-quarkus-testing-unit-tests into .agents/skills/421-frameworks-quarkus-testing-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "421-frameworks-quarkus-testing-unit-tests", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 421-frameworks-quarkus-testing-unit-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/421-frameworks-quarkus-testing-unit-tests .cursor/skills/421-frameworks-quarkus-testing-unit-tests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "421-frameworks-quarkus-testing-unit-tests" agent skill from https://github.com/jabrena/plinth/tree/main/skills/421-frameworks-quarkus-testing-unit-tests into .cursor/skills/421-frameworks-quarkus-testing-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "421-frameworks-quarkus-testing-unit-tests", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jabrena/plinth.git --path skills/421-frameworks-quarkus-testing-unit-tests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 421-frameworks-quarkus-testing-unit-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/421-frameworks-quarkus-testing-unit-tests .gemini/skills/421-frameworks-quarkus-testing-unit-tests && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "421-frameworks-quarkus-testing-unit-tests" agent skill from https://github.com/jabrena/plinth/tree/main/skills/421-frameworks-quarkus-testing-unit-tests into .gemini/skills/421-frameworks-quarkus-testing-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "421-frameworks-quarkus-testing-unit-tests", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jabrena/plinth 421-frameworks-quarkus-testing-unit-testsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/421-frameworks-quarkus-testing-unit-tests .github/skills/421-frameworks-quarkus-testing-unit-tests && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "421-frameworks-quarkus-testing-unit-tests" agent skill from https://github.com/jabrena/plinth/tree/main/skills/421-frameworks-quarkus-testing-unit-tests into .github/skills/421-frameworks-quarkus-testing-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "421-frameworks-quarkus-testing-unit-tests", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 421-frameworks-quarkus-testing-unit-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/421-frameworks-quarkus-testing-unit-tests .opencode/skills/421-frameworks-quarkus-testing-unit-tests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "421-frameworks-quarkus-testing-unit-tests" agent skill from https://github.com/jabrena/plinth/tree/main/skills/421-frameworks-quarkus-testing-unit-tests into .opencode/skills/421-frameworks-quarkus-testing-unit-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "421-frameworks-quarkus-testing-unit-tests", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
421-frameworks-quarkus-testing-unit-tests- GitHub stars
- 447
- Token cost
- ~902 tokens
- SKILL.md length
- 302 words
- Files
- 2 (incl. references)
- Skills in repo
- 124
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI…
- You need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class)
- SKILL.md covers Constraints, When to use this skill, Workflow and Reference
- Calls mvn
- @QuarkusTest with @InjectMock for full CDI mock replacement
What it does
421 Frameworks Quarkus Testing Unit Tests is an agent skill from jabrena/plinth. 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…
Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/421-frameworks-quarkus-testing-unit-tests.md`).
It sits in Testing & QA, covering Unit testing. It works with Java. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.
When your agent uses it
- 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
Example prompts
- “/421-frameworks-quarkus-testing-unit-tests”
What it can do on your machine
Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
421 Frameworks Quarkus Testing Unit Tests loads about 902 tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 236 tokens; SKILL.md has 302 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 302 words, ~902 tokens.
Download SKILL.mdSave it as
.claude/skills/421-frameworks-quarkus-testing-unit-tests/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 421-frameworks-quarkus-testing-unit-tests
- description
- 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
- license
- Apache-2.0
- metadata.author
- Juan Antonio Breña Moral
- metadata.version
- 0.19.0
Quarkus Unit Testing
Apply fast testing strategies for Quarkus: Mockito-first, QuarkusTest when CDI wiring matters.
What is covered in this Skill?
- Pure JUnit 5 + Mockito without container boot (@ExtendWith(MockitoExtension.class))
- @QuarkusTest with @InjectMock for full CDI bean replacement
- @InjectSpy for partial mocking — real bean wrapped as spy, specific methods overridden
- REST Assured for HTTP-level @QuarkusTest resource tests
- @ParameterizedTest with @CsvSource (inline data) and @MethodSource (complex objects)
- QuarkusTestProfile and @TestProfile for test-specific configuration overrides
- Naming conventions: *Test → Surefire (fast phase), *IT → Failsafe (verify phase)
- When to escalate to integration tests (
@422)
Scope: Apply recommendations based on the reference rules and good/bad code examples.
Constraints
Compile before test refactors; verify the full suite after.
- MANDATORY: Run
./mvnw compileormvn compilebefore applying any change - PREREQUISITE: Project must compile before applying test improvements
- SAFETY: If compilation fails, stop immediately
- BLOCKING CONDITION: Compilation errors must be resolved by the user before proceeding
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed rules and examples
When to use this skill
- 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
Workflow
- Read reference and assess project context
Read references/421-frameworks-quarkus-testing-unit-tests.md and inspect the current project setup before proposing changes.
- Gather scope and decide target improvements
Identify requested outcomes, constraints, and the minimum safe set of changes to apply.
- Apply framework-aligned changes
Implement or refactor configuration/code following the reference patterns and project conventions.
- Run verification and report results
Execute appropriate build/tests and summarize what changed, what was verified, and any follow-up actions.
Reference
For detailed guidance, examples, and constraints, see references/421-frameworks-quarkus-testing-unit-tests.md.
© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/421-frameworks-quarkus-testing-unit-tests of jabrena/plinth.
- SKILL.md
- references/421-frameworks-quarkus-testing-unit-tests.md
Open the folder on GitHubat commit dca88dc
Compare with similar skills
421 Frameworks Quarkus Testing Unit Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 421 Frameworks Quarkus Testing Unit Tests this skilljabrena/plinth | 447 | — | ~902 | Automated safety check: Pass | Apache-2.0 | |
| Add Library Testosama-raddad/FireCrasher | 147 | — | ~612 | Automated safety check: Pass | Apache-2.0 | |
| Edt MCP Build TestDitriXNew/EDT-MCP | 295 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Debug Surefireeclipse-rdf4j/rdf4j | 420 | — | ~2.4k | Automated safety check: Pass | BSD-3-Clause | |
| Validationjosstei/maestro-orchestrate | 465 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Minecraft TestingJahrome907/minecraft-agent-skills | 169 | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Edt MCP Build Test
DitriXNew/EDT-MCP
How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo.
Debug Surefire
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
Validation
josstei/maestro-orchestrate
Cross-cutting validation methodology for verifying phase outputs and project integrity
Minecraft Testing
Jahrome907/minecraft-agent-skills
Design and implement automated tests for current Minecraft 26.x or legacy 1.21.x mods and plugins using JUnit, MockBukkit, NeoForge Game Tests, or Fabric Game Tests.
Eclipse Test
gradusnikov/eclipse-chatgpt-plugin
Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods.
More from jabrena/plinth
All 124 skills in this repo703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
Related
Works with
Categories
Questions about 421 Frameworks Quarkus Testing Unit Tests
What does 421 Frameworks Quarkus Testing Unit Tests do?
A skill your agent uses when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI…. 421 Frameworks Quarkus Testing Unit Tests is an agent skill from jabrena/plinth.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).
When should I use 421 Frameworks Quarkus Testing Unit Tests?
421 Frameworks Quarkus Testing Unit Tests fits situations like: 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.
How do I install 421 Frameworks Quarkus Testing Unit Tests in Claude Code?
Run `npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a claude-code`. Or copy the skill folder (skills/421-frameworks-quarkus-testing-unit-tests in jabrena/plinth) into .claude/skills/421-frameworks-quarkus-testing-unit-tests in your project. Claude Code loads it when a task matches its description.
How do I install 421 Frameworks Quarkus Testing Unit Tests in Codex?
Run `npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a codex`. Or copy the skill folder (skills/421-frameworks-quarkus-testing-unit-tests in jabrena/plinth) into .agents/skills/421-frameworks-quarkus-testing-unit-tests in your project. Codex loads it when a task matches its description.
Can I use 421 Frameworks Quarkus Testing Unit Tests in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 421-frameworks-quarkus-testing-unit-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/421-frameworks-quarkus-testing-unit-tests, .gemini/skills/421-frameworks-quarkus-testing-unit-tests, .github/skills/421-frameworks-quarkus-testing-unit-tests and .opencode/skills/421-frameworks-quarkus-testing-unit-tests in your project.
What does 421 Frameworks Quarkus Testing Unit Tests need to run?
Going by SKILL.md and its folder, 421 Frameworks Quarkus Testing Unit Tests needs the command-line tools its instructions call (mvn).
Does 421 Frameworks Quarkus Testing Unit Tests access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 421 Frameworks Quarkus Testing Unit Tests safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does 421 Frameworks Quarkus Testing Unit Tests use?
421 Frameworks Quarkus Testing Unit Tests is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 421 Frameworks Quarkus Testing Unit Tests use?
About 902 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.1k tokens, read only when the agent opens those files.
What are the alternatives to 421 Frameworks Quarkus Testing Unit Tests?
Skills that share tags, products or a category with 421 Frameworks Quarkus Testing Unit Tests: Add Library Test (osama-raddad/FireCrasher, 147 stars), Edt MCP Build Test (DitriXNew/EDT-MCP, 295 stars), Debug Surefire (eclipse-rdf4j/rdf4j, 420 stars) and Validation (josstei/maestro-orchestrate, 465 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 421 Frameworks Quarkus Testing Unit Tests?
jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.
Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.