Code Coverage

Starting with version 2.2.0 the plugin can analyze which lines of esql code have been executed during a message flow test. As input for the analysis the user traces are used. The variable sonar.esql.trace.reportPaths tells the plugin where to look for trace-logs. It's default is target/iibTrace.

Collect user trace

Maven

If the tests are run using maven, the easiest way to collect the trace, is to use the iibTrace-maven-plugin.

manual

Before you start your test run reset the user trace to debug level:

mqsichangetrace <broker_name> -u -e <eg_name> -f <flow_name> -l debug -c 20000 –r

When the test is done, extract the trace log and reset the level to none:

mqsireadlog <broker_name> -u -e <eg_name> -o usertrace.xml
mqsichangetrace <broker_name> -u -e <eg_name> -f <flow_name> -l none -c 20000 –r