The tests are available as regular unit tests and can be simply executed via:
$> sbt testSee io.moia.kamon.log4j2.LoggingTest
At MOIA we use Kamon to set a MDC logging context. A custom data injector io.moia.kamon.log4j2.KamonContextDataInjector is used to achieve this goal. If a context is available, all log statements will print a TraceId to the console. The LoggingTest makes sure, that the MDC is set.
Expectation: the context can be used to set a MDC for logging.
Status: Works!
See io.moia.kamon.SimpleStreamTest
This test uses the most basic akka stream functionality. It combines a source with a map operation that flows to a sink.
Expectation: The context is propagated during the flow.
Status: Works!
See io.moia.kamon.SubStreamTest
This test uses 2 common ways of creating sub-flows. A new context is created in the sub-flow that is later on combined with the outer context.
Expectation: Both inner as well as outer context is propagated during the flow.
Status: Works!
See io.moia.kamon.AsyncStreamTest
This test uses 2 different ways of creating an async boundary. The context is gathered after the async boundary.
Expectation: the context is propagated.
Status: not working.
See io.moia.kamon.CustomStageTest
I implemented a simple custom graph stage for demo purposes: io.moia.kamon.ExampleCustomStage
This test uses a flow with this custom graph stage. The context is gathered after elements are flowing from the custom stage.
Expectation: the context is propagated and available after the custom stage.
Status: not working.
This test uses the GraphDSL to construct a graph where each element flows through several edges of the graph. The context is gathered for all different edges.
Expectation: the context is propagated through all edges.
Status: not working.