Framework for automated integration tests supporting a wide range of message protocols and data formats!
Kafka, Http REST, JMS, TCP/IP, SOAP, FTP/SFTP, SSH, XML, Json and much more!
In a typical test scenario the system under test is running on a test infrastructure while interacting with Citrus over various messaging transports. During the test Citrus is able to act on both sides as client and consumer exchanging real request/response messages over the wire.
With each test step you can validate the exchanged messages with expected control data including message headers, attachments and body content (e.g. XML, Json, ...). The test provides a Java fluent API to specify the test logic and is fully automated. The repeatable test is nothing but a normal JUnit or TestNG test and can easily run as integration test in a CI/CD pipeline.
Apache Camel K is a lightweight integration platform built from Apache Camel. Integrations built with Camel K run natively on Kubernetes and are specifically designed for serverless architectures. With the declarative nature in Camel K users can instantly run integration code written in Camel DSL on their preferred cloud. The presentation outlines typical integration scenarios with Camel K and shows how to write automated tests for these enterprise integrations. The session covers classical service provider/consumer scenarios with common messaging protocols (e.g. REST, JMS, Kafka) as well as more complex integrations with data access and 3rd party Saas services included. The tests itself will also be Cloud Native citizens and make use of Behavior Driven Development concepts.
Joe Colantonio talks to Christoph Deppisch about automate integration tests for pretty much any messaging protocol or data format. So if you’re looking to expand your automation efforts beyond lame, flaky, UI-based automated tests, this episode is for you. Listen to this "testtalks" episode at https://testguild.com/
The concept of behavior driven development (BDD) is quite simple. Business analysts and domain experts describe how the application should behave using Gherkin (given-when-then) feature stories. Developers glue those specifications to automated tests. Can we use this approach when testing the integration of services, too? The talk gives answers with a combination of the frameworks Cucumber and Citrus. After a short introduction to both frameworks we discuss the concepts and see some code examples that demonstrate how the behavior driven approach fits to testing the messaging integration with Http REST, JMS and mail communication. At the end we will have an automated integration test with BDD and almost no glue code to write manually.
The concept of behavior driven development (BDD) is quite simple. Business analysts and domain experts describe how the application should behave using Gherkin (given-when-then) feature stories. Developers glue those specifications to automated tests. The talk combines the frameworks Cucumber and Citrus and gives some code examples that demonstrate how the behavior driven approach fits to testing the messaging integration with Http REST, JMS and mail.
Citrus integrates with frameworks like Apache Camel, Arquillian, Kubernetes and Docker in order to provide automated integration testing of Microservice applications. The tools in action session gives a brief introduction to the Citrus framework and shows code samples for a complete integration test scenario in a Microservices environment.
Your enterprise applications requires detailed integration testing. Citrus provides a tooling for complex integration test with great validation capabilities for XML, JSON and plain text.
See the complete feature list → for details.
See the following reading material and information on Citrus testing.
The reference documentation material for the latest Citrus release is available as online HTML or offline PDF version.