Part two of this tutorial focuses on the creation and interpretation of Clover 'Historical' reports.
On this page:
- Step 1 - Creating history points
- Step 2 - Generating historical data
- Step 3 - Creating historical reports
- Step 4 - Customizing historical reports
- Next steps
Historical reports display graphical and numerical data relating to sets of coverage data collected over time for the project. This tutorial covers the generation of a set of historical data, interpretation of the information displayed in the Historical reports and customization of the reports for your particular reporting preferences.
In the first step, we will edit the Ant build file to generate a history point.
A history point is a snapshot of code coverage and metrics data for the project at a particular point in time. By running tests with Clover over time and creating a series of history points, it is possible to compare code coverage and metrics by viewing results in a single Clover report and enabling you to track the development of your project.
Step 1 - Creating history points
Step 1 describes how to set up the relevant Ant target and run the command so that a history point can be created. The generation of historical reports is discussed in later steps.
Adding a history point target
Add the following target to your
When this target is run, a history point will be created with the timestamp value of the coverage run.
The value of the
historyDir parameter is the directory where the history points will be
stored. You should create this directory before executing this target.
By default, Clover records the history point with
a timestamp of the coverage run. If you wish to override the timestamp value of a history point,
you can add
dateformat attributes to the task allowing you to
reconstruct coverage history. See documentation for the <clover-historypoint> task for details.
Recording a history point
Ensure that the source code has been instrumented, and the tests run, by using the command
clean with.clover test.
Run the command
ant record.point. Output should be similar to the following:
In the next step we will add more tests to improve coverage of the Money library, recording Clover history points along the way.
Step 2 - Generating historical data
In Part 1 of the tutorial we made additions to the testing suite to improve code coverage. In order to show the historical reporter in use, we will now continue to add tests and periodically record history points which will later be used as code coverage and metrics data by the historical reporter.
Money.java file is at 100% coverage, but there are several sections of code that
remain untested in the
MoneyBag.java file. This step will focus on bringing the
coverage of this class to 100%, as well as creating historical data in the form of history points.
Open the source file
MoneyBagTest.java in your favorite text editor and make the
following additions shown in bold:
Declare the variables
fMB3 in the
Add the following test:
After making the above changes, re-instrument and test your code by running
est. Then record a new history point by running
record.point. By recording new history point now, Clover will capture the new state of code
coverage and metrics for comparison with past or future runs.
Add the following tests to bring the coverage of the Money project to 100%:
Once again, re-instrument your code, test and record a new history point.
We have now created a series of history points for the Money library. The next section discusses how to generate a Clover historical report which will display the historical data that has been collected.
Step 3 - Creating historical reports
Now that we have recorded several history points, the next step is to add a target to the build file which will call the historical reporter and generate a historical report.
Add a historical report target
Add the following target to
hist.report target is similar to the
report.html target defined in Part
1. The main differences are that the nested element specifies
<current> and there is no specification of the output format as
The historical reporter needs to be able to find the coverage history files in order to create the
report; so the
historyDir value must be the same as the
for the history points. The format of the report can be either PDF or HTML, as specified by the
<format> element is optional and is not included in the example above. When the
<format> element is omitted, a PDF report is produced by default. Depending on
the chosen format, the
outfile value may represent a single file as in the case of the
PDF format, or the name of a directory (in the case of the HTML format).
Generating a historical report
Create a historical report by using the command
ant hist.report. Output should be
similar to the following:
The report can now be viewed by opening the file
tutorial/historical.pdf in a PDF viewer
such as Adobe Acrobat
To interpret this history report, see Understanding a Historical Report
Step 4 - Customizing historical reports
In the previous sections of this tutorial we have looked at how to create and interpret a basic
historical report. In addition to basic reporting, the historical reporter is highly configurable
and this section will detail some of the options you can use. For a full list of the report
configuration options, see the documentation for the
Changing output format
The default historical report type is PDF, although an HTML report can also be produced. To create an
HTML report, add a nested
<format> element with type specified as
html to your
<clover-report> element. Try adding the
following target to your
build.xml file and executing the command
A custom title can also be displayed for your report by using the
title attribute in the
<historical> element as above. You can find report in
The historical reporter allows you to specify which charts to include in your report, and also allows you to configure further options in the charts themselves.
The default reporting mode is to include all four report elements:
<movers>. But to
include some and not the others is a simple matter of nesting the desired elements within the
element. Try adding the following target to your
build.xml file as an example:
The above code will produce a historical PDF report with the title '
My Project' which
includes only two sections: the 'Overview' and the 'Coverage over time' charts.
Clover presents flexible charting configuration, allowing you to present information exactly as you
like it. The
<chart> element allows you to define a custom chart and fill it with
specific data with the
This will produce a PDF file with the filename '
histSelect.pdf' with two sections: the a
custom chart with total coverage information; and the 'Metrics over time' chart. You can also
specify whether or not a chart uses a log scale by adding the
The 'Movers' section of the historical report shows you the classes whose coverage has changed the most recently. This is useful for spotting classes that have had sudden changes in coverage, perhaps the unintended result of changes to the unit test suite.
The 'Movers' chart allows you to specify the threshold of point change a class must satisfy, the
maximum number of gainers and losers to display and the period across which the gains and losses are
calculated. Add the following target to your
build.xml file as an example of this
feature in use:
In this case, the configuration values selected state that classes must have a change in coverage of at least 5 percentage points to be included in the chart, a maximum of 20 gainers and 20 losers can be displayed, and the initial valuation point for class coverage is 2 weeks prior to the most recent history point. Should there be greater than 20 gainers in this period, then the classes with the biggest percentage point gain will be displayed, and the same for the losers.
See Interval Format for details on the syntax for specifying interval values.
The next section of this tutorial will discuss how you can automate the coverage checking of your project.