A Kubernetes-native open-source platform for API mocking and contract testing from OpenAPI, AsyncAPI, gRPC, GraphQL, and Postman assets.
Microcks is an open-source, cloud-native tool for API mocking and testing. It turns API specifications like OpenAPI, AsyncAPI, gRPC, GraphQL, and Postman collections into live mocks and uses them for automated contract and non-regression testing. It solves the problem of API dependency and reliability in microservices and distributed systems development.
API developers, test engineers, and DevOps teams building and maintaining microservices or distributed systems who need to mock dependencies and ensure API contract compliance.
Developers choose Microcks for its ability to generate mocks from multiple specification formats instantly and integrate contract testing into CI/CD pipelines, reducing development cycles and preventing breaking changes.
The open source, cloud native tool for API Mocking and Testing. Microcks is a Cloud Native Computing Foundation sandbox project 🚀
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Imports OpenAPI, AsyncAPI, gRPC, GraphQL, Postman, and SoapUI projects, allowing teams to reuse existing API artifacts without conversion headaches.
Generates executable API mocks in seconds from specifications, enabling parallel development and reducing dependency wait times in microservices.
Runs conformance and non-regression tests against implementations, ensuring API reliability and preventing breaking changes in CI/CD pipelines.
Provides CLI and integrations with Jenkins, GitHub Actions, and Tekton, making it easy to automate testing and validation in modern DevOps workflows.
Designed as a cloud-native platform, deployment and management in non-Kubernetes environments require additional configuration and can be cumbersome.
Effectiveness hinges on accurate and complete API specifications; incomplete or poorly maintained specs can lead to misleading mocks and test failures.
Requires integration into existing toolchains and workflows, which may involve a learning curve and configuration effort for teams new to specification-first approaches.