Citrus vs Microcks

Citrus is a free integration-test framework for messaging applications and microservices. It can make a test act as both client and server across messaging interfaces, send and sequence messages, and validate payloads and other elements. Supported endpoints include HTTP, Kafka, JMS, Apache Camel, mail, FTP/SFTP, OpenAPI, SOAP, Docker, Kubernetes, Knative, SQL, and SSH. Validation covers JSON and XML, XML schemas, DTDs, and database data. Test cases can use loops, delays, retries, parallel sections, and timeouts. Tests are written in Java, XML, YAML, or Cucumber BDD features. Citrus integrates with JUnit 5, Cucumber, JBang, Quarkus, Spring Boot, TestNG, and JUnit 4, with Maven and Gradle setup guidance. It runs on Linux and requires Java 17 or newer since version 4.0. Citrus is Apache-licensed freeware for testing commercial applications.

Microcks is an open-source tool for mocking and testing APIs and microservices. It works with OpenAPI, AsyncAPI, gRPC/Protobuf, GraphQL schemas, and SOAP, and can build mock responses from examples, generate realistic data, or alter mock data and responses dynamically. It also checks provider and consumer contracts against live implementations and specification versions, and automates checks in CI/CD pipelines with integrations for GitHub Actions, Jenkins, GitLab CI, and Tekton. Containerized deployment supports on-premises, cloud, and developer-laptop use; its Uber distribution is intended for laptop work and unit tests, using ephemeral in-memory MongoDB. The free, community marketplace for API mocks and test suites is enabled by default. Microcks is a CNCF incubating project, with a listed price of free. The public demo is read-only and cannot import APIs or change artifacts. Documentation cautions against production use of the all-managed Kubernetes setup because its single Keycloak and MongoDB instances are not tuned for scalability or security best practices.