Creator of the Karate Test Automation Framework
One of the features in the works (and close to being released) is the ability to spin-up test-doubles to “mock” a web-service API dependency that may still be in development — or for which a test-environment may be un-available or unstable. This is a significant pain-point for many teams — and “flaky integration tests” are legendary sources of pain for many a platform team dealing with micro-services.
You can find a comprehensive list of capabilities in the project-documentation. While the README evolves, a demo end-to-end example using Spring Boot has been created as an early preview for the community, and is summarized below.
We use a simplified example of a Java ‘consumer’ which makes HTTP calls to a Payment Service (provider) where
DELETE have been implemented. The 'provider' implements CRUD for the
Payment.java 'POJO', and the
POST (or create) results in a message (
Shipment.java as JSON) being placed on a queue, which the consumer is listening to.
ActiveMQ is being used for the sake of mixing an asynchronous flow into this example, and with the help of some simple utilities, we are able to mix asynchronous messaging into a Karate test as well as the test-double.
Karate on the ‘other side of the fence’ (handling HTTP requests instead of making them) — turns out to be remarkably effective, yet simple.
If you think about it, all the above are sufficient to implement any micro-service. Karate’s DSL syntax is focused on exactly these aspects, thus opening up interesting possibilities.
It may be hard to believe that you can spin-up a ‘usable’ micro-service in minutes with Karate — but do try it and let me know what you think !