Configuring Access To Test Coverage Reports From Parabuild

This technical note discusses setting up access to Clover reports through Parabuild Web UI.

Using Clover in Automated Builds

Clover is a popular test coverage tool. Test coverage metrics provided by Clover allow to identify and to fix gaps in unit tests.

Running test coverage as a part of an automated build and test sequence executed by Parabuild either continuously or on a daily basis allows for early feedback on test coverage. Parabuild supports collecting, archiving and showing through its Web UI various types of logs, including single file logs and reach HTML logs. This makes Parabuild a natural place to gather and to present to the software team the following Clover reports:

Configuring access to these Clover reports in Parabuild is a trivial exercise. Details are discussed in the following sections.

Configuring Access To Detailed Coverage Reports in HTML Format

As you already know, a detailed coverage report is created using <clover-report> task:

<target name="clover.report" depends="with.clover">
   <mkdir name="temp/clover_html_report">
   <clover-report>
      <current outfile="temp/clover_html_report">
         <format type="html"/>
      </current>
   </clover-report>
</target»

To make this report available through Parabuild Web UI we have to configure a build log of type "Directory with HTML files":

  1. Log in to Parabuild as admin user
  2. Open the build configuration for edit and select "Logs" tab
  3. Select "Directory with HTML files" log type
  4. Click "Add" button
  5. Fill log description (we recommend "Clover coverage")
  6. Enter log path (in our case it is "tem/clover_html_report")
  7. Enter "index.html" as an index file

 

Click on "Save" button. That's it. Next time build runs the log will be placed into Parabuild's log archive and made available to the whole team:

 

 

Parabuild users will click on the Clover coverage link and a full-blown Clover HTML report will pop up: