Version 0.2.0 of Kafka for Junit has been released. It features a couple of small improvements to the code and documentation, as well as the addition of ExternalKafkaCluster, which is an abstraction that allows you to use the same convenient accessor interfaces that you are already familiar with when interacting with embedded Kafka clusters, against external Kafka clusters.

The first version of Kafka for JUnit has been released. It features a customizable embedded Kafka broker setup with Kafka Connect and a rich set of convenient accessors to interact with the cluster.

What if there is no module on the module path that provides a suitable implementation of Matcher? What if there is no implementation of that interface at all? In this case, it is possible to provide a default implementation alongside the public API. The benefit is, that once the API module is distributed, it can definitely be put to use, even if the default implementation does not exhibit the quality aspects that we aimed for. Providing a default implementation is quite simple.