quarkus-tdd
Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.
npx skills add mturac/everything-openai-codex --skill quarkus-tdd --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides developers on test-driven development for Quarkus 3.x services, emphasizing high coverage and event-driven testing. The workflow covers writing failing tests first, implementing minimal code to pass, and refactoring with green tests, plus enforcing 80%+ JaCoCo coverage. It includes testing for REST endpoints, bug fixes, refactors, reactive streams, Camel routes, RabbitMQ events, and async operations, with patterns for organizing tests and ensuring proper interactions.
How it works
- Start by writing tests first so they fail, then implement minimal code to pass, and refactor with tests green.
- Enforce 80%+ coverage via JaCoCo.
- Use a nested test structure to group tests by method or feature, with @Nested classes and @DisplayName for readable reports.
- Follow naming conventions like givenX_whenY_thenZ and AAA comments (ARRANGE, ACT, ASSERT).
- Provide comprehensive coverage, including happy paths, null inputs, edge cases, and exception handling.
- Verify interactions with mocks using verify(), and use never() where appropriate.
- Include testing patterns for Camel routes and event services, demonstrating approach with examples.
When to use it
- New features or REST endpoints
- Bug fixes or refactors
- Adding data access logic, security rules, or reactive streams
- Testing Apache Camel routes and event handlers
- Testing event-driven services with RabbitMQ
- Testing conditional flow logic
- Validating CompletableFuture async operations
- Testing LogContext propagation
What it can touch
- Java tests following the described structure and annotations
- Mockito mocks and @InjectMocks patterns
- Camel testing utilities (CamelContext, ProducerTemplate, MockEndpoint, AdviceWith)
- JUnit 5, AssertJ, and Mockito interactions
- JaCoCo for coverage enforcement
Caveats
- The skill outlines a testing strategy and patterns but does not guarantee test outcomes.
- It assumes familiarity with Quarkus 3.x, JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo.
- License is MIT.
# Quarkus TDD Workflow TDD guidance for Quarkus 3.x services with 80%+ coverage (unit + integration). Optimized for event-driven architectures with Apache Camel. ## When to Use - New features or REST endpoints - Bug fixes or refactors - Adding data access logic, security rules, or reactive streams - Testing Apache Camel routes and event handlers - Testing event-driven services with RabbitMQ - Testing conditional flow logic - Validating CompletableFuture async operations - Testing LogContext propagation ## Workflow 1. Write tests first (they should fail) 2. Implement minimal code to pass 3. Refactor with tests green 4. Enforce coverage with JaCoCo (80%+ target) ## Unit Tests with @Nested Organization Follow this structured approach for comprehensive, readable tests: ```java @ExtendWith(MockitoExtension.class) @DisplayName("OrderService Unit Tests") class OrderServiceTest { @Mock private OrderRepository orderRepository; @Mock private EventService eventService; @Mock private FulfillmentPublisher fulfillmentPublisher; @InjectMocks private OrderService orderService; private CreateOrderCommand validCommand; @BeforeEach void setUp() { validCommand = new CreateOrderCommand( "customer-123",
- When to Use
- Workflow
- Unit Tests with @Nested Organization
- Key Testing Patterns
- Testing Camel Routes
- Testing Event Services
- Testing CompletableFuture
- Resource Layer Tests (REST Assured)
- Integration Tests with Real Database
- Coverage with JaCoCo
- Maven Configuration (Complete)
- Test Dependencies
- Best Practices
- Test Organization
mvn clean test mvn jacoco:report mvn jacoco:check Report at: target/site/jacoco/index.html
What does the quarkus-tdd skill do?
Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill quarkus-tdd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.