Quarkus TDD
Test-driven development for Quarkus 3.x: JUnit 5, Mockito, @Nested organization, Camel route testing, REST Assured, and JaCoCo 80%+ coverage enforcement.
- What
- Test-driven development for Quarkus 3.x: JUnit 5, Mockito, @Nested organization, Camel route testing, REST Assured, and JaCoCo 80%+ coverage enforcement.
- Cost
- Free
- Needs
- none to install. A Quarkus 3.x project with Maven helps; have the feature or bugfix in mind.
- Level
- Beginner
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a test-driven development workflow for Quarkus 3.x services that keeps Muse writing tests first and coverage high. The loop is explicit: write failing tests, implement the minimum to pass, refactor while green, enforce 80%+ line coverage (70%+ branch) with JaCoCo. Unit tests follow a strict shape: @Nested classes grouped by method under test, @DisplayName for readable reports, given/when/then naming, AAA comments, AssertJ assertions, and Mockito verify() including never() for error paths. Goes deep on event-driven testing: Apache Camel routes tested with AdviceWith and MockEndpoint (replacing RabbitMQ endpoints with mocks, weaving assertions into routes), event services with success and error event verification, CompletableFuture async operations including LogContext propagation, and REST Assured resource tests for the HTTP layer. Integration tests use @QuarkusTest with real databases via test profiles, and the Maven setup (dependencies, JaCoCo prepare-agent/report/check) is spelled out copy-ready. Use when adding features, fixing bugs, or refactoring Quarkus services, especially event-driven ones. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: aimed at Quarkus 3.x LTS, adjust for other versions; Camel route testing has real learning curve, the examples help but expect setup friction; 80% coverage is a floor for discipline, not a guarantee of correctness. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Quarkus TDD is a free skill for Muse. a test-driven development workflow for Quarkus 3.x services that keeps Muse writing tests first and coverage high. The loop is explicit: write failing tests, implement the minimum to pass, refactor while green, enforce 80%+ line coverage (70%+ branch) with JaCoCo.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Quarkus TDD" with your Muse. Prerequisites: none to install. A Quarkus 3.x project with Maven helps; have the feature or bugfix in mind. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/quarkus-tdd/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Let's do TDD for this: [describe the feature or bug]. Write the failing test first." 3. Ask it to organize tests in @Nested classes with given/when/then names and AAA comments, and to keep coverage above 80%. Tip: for Camel routes, ask it to show the AdviceWith/MockEndpoint test before touching the route. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated tests: a passing bad test is worse than no test.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.