5.2 Adding EMMA Report

Added by Steve Luo, edited by Lubos Pochman on Aug 28, 2008 show comment
You are viewing an old version (v. 12) of this page.
The latest version is v. 30, last edited on Aug 06, 2009 (view differences | )
<< View previous version | view page history | view next version >>

To add EMMA report, you only need two steps:

  1. Generate EMMA XML report from Ant or Maven or any other build tool.
  2. Publish EMMA report in the [configuration].

Generate EMMA Report

QuickBuild will NOT generate EMMA report automatically, so first make sure that the EMMA report is produced by ANT or by any other build tool. The following example shows how to generate EMMA [code coverage] by Ant EMMA task:

EMMA target in build.xml
<target name="emma_coverage">
    <emmajava enabled="${emma.enabled}" libclasspathref="emma.lib"
              filter="${emma.filter}" sourcepath="${src.dir}"
              classname="Main" classpathref="run.classpath">
      <arg value="someargvalue" />

      <xml outfile="reports/emma/coverage.xml" />
    </emmajava>
</target>

The code snippet will generate the XML report for all the source code. XML report coverage.xml will be generated in 'reports/emma directory' directory which is relative to the [workspace] directory.

After adding the target above, generate the XML code coverage report for your source code, and after that you can tell QuickBuild to publish the results.

Publish EMMA Report

Just like all other [build reports], you can add EMMA report by [adding a publish step] in a [configuration]. When you add publish EMMA Report step, the following screen will be displayed:

Unable to render embedded object: File (emma_step.png) not found.

In source files field, QuickBuild uses Ant style file patterns to collect the reports, and the directory you specified is relative to the [workspace] directory.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.