Microcks

microcks.io ↗

Turns API definitions and collections into mocks, then runs contract-conformance and non-regression tests.

SI Score
75/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Microcks

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Microcks homepage

What it does

Microcks is an open-source tool for mocking and testing APIs and microservices. Its repository describes importing OpenAPI, AsyncAPI, gRPC, GraphQL, Postman, and SoapUI assets to produce live mocks, then reusing those assets for conformance and non-regression tests against an implementation. It also documents CI integrations through a CLI. A team can use it to provide a simulated dependency before an API is ready, then check the implementation against the same contract later.

Start with the contract you need to exercise

A practical first task is to supply an API definition or collection for a dependency that is not yet available. Microcks can turn that asset into a live mock so a consumer team can integrate against a stable contract, then reuse the same material for conformance or non-regression tests against the implementation. The scenario is illustrative; no mock was created and no request was sent for this listing.

The official repository lists support for OpenAPI, AsyncAPI, gRPC protobuf, GraphQL schemas, Postman collections, and SoapUI projects, and describes integrations with Jenkins, GitHub Actions, Tekton, and other CI systems through a CLI. Bring the contract artifact, the service implementation when ready, and a running Microcks instance.

The repository README was accessible, but the public product home and documentation landing page returned title-only responses in this research pass, so current deployment instructions and managed-service availability or pricing could not be verified. This entry is limited to capabilities documented in the official repository README and license.

Strengths

  • Generates mocks from multiple API specifications and collection formats.
  • Reuses API assets for conformance and non-regression testing against an implementation.
  • Documents CI integrations through a CLI.

Best for

  • Unblocking consumer development with mocks based on an API contract.
  • Checking whether an API implementation conforms to its OpenAPI, AsyncAPI, GraphQL, or gRPC description.
  • Running API mock and conformance workflows within an existing CI pipeline.

Sources