quarkus-tdd

Topics in the source

• Quarkus TDD Workflow
• When to Use
• Workflow
• Unit Tests with @Nested Organization
• Key Testing Patterns
• Testing Camel Routes
• Testing Event Services
• Testing CompletableFuture

TDD guidance for Quarkus 3.x services with 80%+ coverage (unit + integration). Optimized for event-driven architectures with Apache Camel. 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 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) Follow this structured approach for comprehensive, readable tests: 1. @Nested Classes: Group tests by method being tested 2. @DisplayName: Provide readable test descriptions for test reports 3. Naming Convention: givenXwhenYthenZ for clarity 4. AAA Pattern: Explicit // ARRANGE, // ACT, // ASSERT comments 5. @BeforeEach: Setup common test data to reduce duplication 6. assertDoesNotThrow: Test success scenarios without catching exceptions 7. assertThrows: Test exception scenarios with message validation using AssertJ 8. Comprehensive Coverage: Test happy paths, null inputs, edge cases, except

This is an excerpt. Refer to the complete source and its current requirements.