Microcks vs Wilma

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.

Wilma is free, GPLv3-or-later software for developing and testing applications that depend on other services. It combines a service stub with an HTTP/HTTPS transparent proxy, allowing teams to capture, decode, save, and forward traffic, including two-way SSL, or generate configured responses. It can operate as a proxy, a stub, or both. JSON files define stub behavior, and configurations can be uploaded or changed through the interface or service while Wilma runs. Real-time interceptors can inspect or modify requests and responses; custom interceptors, condition checkers, and response formatters can be added, including through classes or JAR files. Message Search finds logged request-response pairs. Wilma supports unit, integration, functional, end-to-end, performance, and manual testing. It is available as Docker images, GitHub release ZIP files, or source builds. The application requires JRE 11, while Message Search requires JDK 11. Logging can be controlled and old logs deleted on schedules.