Feature: Asynchronous Order Processing Scenario: Customer places an order and receives confirmation Given I have a Kafka endpoint "orderInput" When I send a "CreateOrder" message Then I expect a "OrderValidated" message on "kafka.output" within 5 seconds And I expect a "EmailSent" message on "smtp.mock" within 10 seconds Use code with caution.
To simplify the testing of complex, asynchronous, multi-step messaging flows where the order of messages is not guaranteed, and the response happens via a different channel than the request. 2. Key Components to Develop: Citrus
Allows users to define a sequence of expected events in a cucumber.feature file without writing Java glue code, enabling them to assert that messages A, B, and C arrived within a specific timeframe, even if they arrived out of order. Key Components to Develop: Allows users to define
This feature enhances Citrus’s ability to test modern microservices architectures that rely heavily on event-driven messaging (e.g., Kafka, RabbitMQ) rather than synchronous HTTP requests. Feature Proposal: Asynchronous Event-Driven Validation Leverage existing com
Automatically detects and correlates asynchronous messages based on headers (e.g., correlation-id , message-id ) across different transports (Kafka to HTTP, JMS to Kafka).
Leverage existing com.consol.citrus.kafka and com.consol.citrus.jms libraries.