As of today (version 0.1.4 of this library) we just support essential features of Microcks provided by the main Microcks container. The list of supported features is the following:
Mocking of REST APIs using different kinds of artifacts,
Contract-testing of REST APIs using OPEN_API_SCHEMA runner/strategy,
Mocking and contract-testing of SOAP WebServices,
Mocking and contract-testing of GraphQL APIs,
Mocking and contract-testing of gRPC APIs.
Asynchronous API mocking and ASYNC_API_SCHEMA contract-testing strategy are not supported at the moment as it would require an additional microcks-async-minion container as well as a Kafka broker to ensure communication with the main container.
Description
We'd like to extend the notion of MicrocksContainersEnsemblewe described in #24 to also allow the usage of Microcks asynchronous features.
Implementation ideas
Ideally, we should be able to manage 2 different modes:
the one we're providing a Kafka broker because the user doesn't care (typically, we'll use a RedPanda testcontainer here)
the one we're reusing a Kafka broker that the user has initialized. In that case, we may want/need to reuse or share the same docker network and also have loose-coupling just reusing a broker bootstrap URL to connect everything
Reason/Context
As of today (version
0.1.4
of this library) we just support essential features of Microcks provided by the main Microcks container. The list of supported features is the following:Asynchronous API mocking and
ASYNC_API_SCHEMA
contract-testing strategy are not supported at the moment as it would require an additionalmicrocks-async-minion
container as well as a Kafka broker to ensure communication with the main container.Description
We'd like to extend the notion of
MicrocksContainersEnsemble
we described in #24 to also allow the usage of Microcks asynchronous features.Implementation ideas
Ideally, we should be able to manage 2 different modes: