anchor.diff:  <3> Use `KafkaTestUtils` to quickly consume messages.
   <4> The `KafkaConditions` integrates with AssertJ to make received messages simpler.
   
  -To me this library lacks some syntactic sugar to make tests more readable.
  +Spring Kafka Test is probably the way to go when you're developping a Spring application. 
  +However this library lacks some syntactic sugar to make tests more readable.
   
   == Kafka in docker
   
  
positive.code: 
  == Kafka embedded in the test
  
  As both Kafka and Zookeeper are Java applications, it is possible to control them by calling their code. It is possible (have a look at https://github.com/apache/camel/blob/master/components/camel-kafka/src/test/java/org/apache/camel/component/kafka/embedded/EmbeddedKafkaBroker.java[camel-kafka] or https://github.com/danielwegener/logback-kafka-appender/blob/master/src/test/java/com/github/danielwegener/logback/kafka/util/EmbeddedKafkaCluster.java[logback-kafka-appender]), but is not easy.
  
  There are many libraries to run an embedded Kafka from JUnit without sweating:
  
  * https://github.com/charithe/kafka-junit[Kafka JUnit] by Charith Ellawala
  * Another https://mguenther.github.io/kafka-junit/[Kafka JUnit] by Markus Günther
  * https://docs.spring.io/spring-kafka/docs/2.2.6.RELEASE/reference/html/#testing[Spring Kafka Test] by the Spring team
  
  === Kafka JUnit
  
  
negative.code: <1> Load JUnit 5 extension that will start an embedded Kafka
  <2> A `kafkaHelper` is injected to get embedded Kafka address
  
  This `KafkaHelper` contains several methods to easily produce and consume messages
  [source,java]
  ----
  include::{sourcedir}/src/test/java/com/github/gquintana/kafka/CharitheMessageServiceIT.java[tags=api]
  