For AI agents: the complete documentation index is available at llms.txt; every page is also available as Markdown by appending .md to its URL.
Skip to main content

Microcks 1.16.0 release ๐Ÿš€

ยท 8 min read
Laurent Broudoux
Co-founder of Microcks | Director of Engineering at Postman Open Technologies

We are excited to announce the 1.16.0 release of Microcks, the CNCF's open-source cloud-native tool for API Mocking and Testing! ๐Ÿš€

Your API landscape rarely fits into a single tool or messaging platform. A collection created in Bruno, an enterprise application using IBM MQ, and a cloud service exchanging messages over Google Pub/Sub can all be part of the same business flow. Testing these systems means connecting those worlds without making your development environment harder to run.

That's the common thread of Microcks 1.16.0: more connections, less waiting! This release opens new routes into your API simulation environment while making Microcks itself faster to start. To illustrate these new connections and faster starts, we chose a bridge carrying trails of light into the sunrise:

Light trails crossing a bridge at sunrise in Sweden

Here are the highlights:

  • OpenCollection support brings a new source of API mocks, especially for teams using Bruno.
  • Docker Hardened Images and Java 25 AOT caching give our JVM-based containers a new foundation and faster startup.
  • IBM MQ support extends AsyncAPI mocking and testing to another enterprise messaging platform.
  • Google Pub/Sub request/reply lets you simulate asynchronous conversations, not just independent events.
  • Improved Avro handling and Avro binary publishing over NATS make event-based mocks and contract tests more reliable.

Let's take a closer look!

OpenCollection: bring your Bruno examples to Microcksโ€‹

API collections are a natural place to capture the requests and responses your team uses every day. With this release, Microcks supports OpenCollection as a new import format for mocks. This open, YAML-based format pioneered by Bruno opens the door to reusing your API client examples in a shared simulation environment.

Instead of maintaining a separate set of mock examples, you can reuse examples from an OpenCollection document in Microcks. The import also computes dispatching criteria so that those examples can be selected and served by the mocking engine. Your collection becomes useful beyond your API client: teammates and automated tests can consume the resulting mock endpoints.

This continues a core Microcks principle: reuse the API artifacts you already maintain, rather than rewrite them for a dedicated mocking tool.

Thanks to SebastienDegodez ๐Ÿ™ for the OpenCollection contributions! See the example import work and the dispatching enhancement for implementation details.

A hardened foundation, ready to start fasterโ€‹

Short-lived development environments and CI jobs shouldn't spend unnecessary time waiting for their mocking infrastructure. Microcks 1.16.0 updates the default JVM-based webapp and uber container images with Docker Hardened Images, Java 25, and a Project Leyden AOT cache.

The new runtime is based on a distroless Docker Hardened Image: it runs as a non-root user and has no shell. Alongside this smaller runtime surface, the image build now includes a training step that prepares a JVM ahead-of-time cache. Java reuses that cache at startup, reducing the work needed to load and link application classes.

This is a JVM optimization, not a native executable. It brings faster startup to the JVM-based distributions while retaining their Java runtime and support for custom libraries.

Early measurements reported in the DHI implementation issue, with 1 CPU and 512 MB of memory, showed startup times of around 2.2 seconds for the webapp and 2.6 seconds for the uber distribution. These are measurements from that setup, not a performance guarantee for every deployment.

Upgrading customized deployments? The new images no longer include run-java.sh, so its JAVA_OPTIONS mechanism is gone. Review your JVM settings and use JAVA_TOOL_OPTIONS or JDK_JAVA_OPTIONS as appropriate. Custom probes or scripts that rely on a shell or curl inside the container also need updating. See the DHI migration details and the Leyden AOT cache work.

IBM MQ joins the AsyncAPI bindingsโ€‹

Modernizing an application doesn't mean leaving its existing messaging infrastructure behind. IBM MQ is now supported as an AsyncAPI binding in Microcks, bringing API simulation and contract testing to teams working with this enterprise messaging platform.

This release adds both mocking and testing support, including queue and topic scenarios. You can describe your messages with AsyncAPI, use Microcks to simulate producers, and check messages from your implementation against the contract. The integration also includes UI support and Helm configuration for deployment.

For teams connecting established enterprise systems to newer services, this means one more part of the architecture can join the same contract-driven testing workflow.

Thanks to alokkumardalei-wq ๐Ÿ™ for the IBM MQ contributions! Explore the work on mocking, contract testing, and Helm setup.

Google Pub/Sub: from events to conversationsโ€‹

Not every asynchronous interaction is fire-and-forget. Sometimes a service publishes a request and expects an answer on another channel, with enough context to connect the two messages.

Microcks 1.16.0 extends its AsyncAPI request/reply mocking capabilities to Google Pub/Sub. You can now simulate a responding service over Pub/Sub, allowing consumers to exercise a request/reply flow without waiting for the real service to be available.

This builds on the request/reply capabilities introduced in previous releases and brings them to another messaging ecosystem. It's especially useful when your integration tests need a conversation with a dependency rather than a periodic stream of sample events.

Follow the Google Pub/Sub request/reply implementation for details.

Avro: more reliable contracts and binary mocksโ€‹

Better schema parsing, serialization, and validation feedbackโ€‹

Binary message formats need careful handling: a schema parsing problem or an invalid payload should produce useful feedback, not leave you wondering whether your broker is reachable.

This release improves Avro schema parsing for AsyncAPI 3.0 Multi Format Schema Objects, including inline schemas and external schema references. It also improves union handling during serialization and decoding, and the reporting of parsing and validation errors. These changes address cases where Avro errors could interrupt a test before its result was reported.

The result is more reliable Avro mocking and contract testing, with better feedback when a schema or message needs attention.

See the Avro issue and resolution. Thanks to drazen-nikolic ๐Ÿ™ for the detailed reproducer and investigation!

Avro binary publishing over NATSโ€‹

The NATS binding now publishes Avro-encoded mock messages when an Avro binary content type is declared. Previously, those examples were published as JSON text, which Avro consumers could not decode as expected.

Together with the schema handling improvements, this lets you use AsyncAPI 3.0 contracts with Avro payloads over NATS for both mock publishing and message validation.

Encoding note: NATS publishes raw Avro binary, without a schema registry envelope. Non-Avro content types are unchanged. Thanks to [drazen-nikolic] ๐Ÿ™(https://github.com/drazen-nikolic) for contributing this enhancement and testing it against a real broker!

Other improvementsโ€‹

There are more enhancements beyond these highlights, including:

For the detailed list of changes used to prepare this announcement, check the 1.16.0-rc1 release notes and the 1.16.0 milestone.

What's coming next?โ€‹

More connections, less waiting: we look forward to seeing what you build with these new formats, bindings, and runtime improvements. Tell us how they work in your environment, especially as you adopt the new container images or bring IBM MQ and Avro-based flows into your tests.

Thank you to all the contributors and adopters who helped shape this release through code, bug reports, reproductions, and feedback!

We will continue to prioritize improvements with the community. Join our GitHub discussions, explore the issues and roadmap, or come say hi on Discord.

Send some love through GitHub stars, and follow us on Bluesky, LinkedIn, and YouTube for more examples and demonstrations.

Thanks for reading and supporting us! โค๏ธ