Rule Set Coverage Tool

CER includes a tool to report on the parts of a rule set that are "covered" are runtime. Coverage statistics can be reported for any processing which requests values from CER, including:

the running online application; and
executions of JUnit tests.

To capture coverage data, set the environment property curam.creole.coverage.logfile (in Bootstrap.properties) to the location of a file. As rules execute, lines containing coverage information will be appended to the file when CER expressions are evaluated.

Tip: To clear the coverage data, just delete the file specified in your curam.creole.coverage.logfile setting.

Over time, the coverage data file can become big, so you should turn off the capturing of coverage data when not required, by removing (or commenting out) your curam.creole.coverage.logfile setting.

To create a coverage report, run the following target:

build creole.report.coverage -Dfile.coverage.log= file location

A simple color-coded drillable report will be written to .../EJBServer/build/svr/creole.gen/coverage/index.html, where

Green = covered
Yellow = partially covered
Red = not covered

Rule attributes with a derivation of <specified> are intentionally excluded from the report. A sample report is shown below:

Figure 1. Example Coverage Report

Note that rule sets and classes which are "included" in other rule sets (using the <Include> mechanism) essentially become part of the source of the outermost including rule set. This should be borne in mind when analyzing coverage reports.