7.1 Adding JUnit Report

compared with
Version 38 by Steve Luo
on Jun 06, 2009 08:22.


Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 To add [JUnit|http://www.junit.org] report, you only need two steps:
 # Generate JUnit *XML* report from [Ant|http://ant.apache.org] or [Maven|http://maven.apache.org] or any other build tool.
 # Publish JUnit report in the [configuration|1. Working with Configuration].
  
 h2. Generate JUnit Report
  
 QuickBuild will NOT generate [JUnit|http://www.junit.org] report automatically, so first make sure the [JUnit|http://www.junit.org] report is produced by [ANT|http://ant.apache.org] or by any other build tool. The following example shows how to generate JUnit test results with [Ant JUnit task|http://ant.apache.org/manual/OptionalTasks/junit.html] and aggregate all the test reports into one by using [Ant JUnitReport task|http://ant.apache.org/manual/OptionalTasks/junitreport.html] (this is not required):
 {code:xml|title=JUnit target in build.xml}
 <target name="junit" depends="compile.test">
  <mkdir dir="${junit.report.dir}" />
  <mkdir dir="${junit.report.dir}/test-out" />
  <record name="${junit.report.dir}/test-output.txt" append="no" action="start"/>
  <junit printsummary="yes" haltonfailure="false" fork="yes">
  <classpath refid="test.classpath"/>
  <formatter type="xml"/>
  <batchtest fork="yes" todir="${junit.report.dir}/test-out">
  <fileset dir="${test.home}">
  <include name="**/*Test.java"/>
  <exclude name="**/*AbstractTest.java"/>
  </fileset>
  </batchtest>
  </junit>
  <junitreport todir="${junit.report.dir}">
  <fileset dir="${junit.report.dir}/test-out">
  <include name="TEST-*.xml"/>
  </fileset>
  </junitreport>
  <record name="${junit.report.dir}/test-output.txt" action="stop"/>
 </target>
 {code}
 The code snippet will generate the XML reports for each test case, and the reports will be captured to '$\{junit.report.dir\}' directory.
  
 {note:title=About haltonfailure}
  If 'haltonfailure' in junit task is defined to true, Quickbuild may not publish the JUnit reports completely. So the best practice here is set 'haltonfailure' to false.
  If 'haltonfailure' in junit task is defined to true, the junit reports are not complete. If you want to generate the full reports, set 'haltonfailure' to false.
 {note}
  
 h2. Publish JUnit Report
  
 Just like all other [build reports|07. Publish Build Reports], you add JUnit report by [adding a publish step|Working With Step] in a [configuration|1. Working with Configuration]. When you add publish JUnit Report step, the following screen will be displayed:
  
 !Screenshots^report_publish_step.png!
  
 In source files field, QuickBuild uses Ant style file patterns to collect the reports, and the directory you specified is *relative* to the [workspace|Workspace Directory] directory.
  
 If you have several report sets, you can add several publish JUnit steps with different report set names.