JUnitReport

Merge the individual XML files generated by the JUnit task and eventually apply a stylesheet on the resulting merged document to provide a browsable report of the testcases results.

Requirements

You need Xalan 1 to use this task or use the Xalan1 compatibility jar of Xalan2.

Parameters

Attribute	Description	Required
tofile	The name of the XML file that will aggregate all individual XML testsuite previously generated by the JUnit task.	No. Default to TESTS-TestSuites.xml
todir	The directory where should be written the file resulting from the individual XML testsuite aggregation.	No. Default to current directory

Nested Elements

fileset

junitreport collects individual xml files generated by the JUnit task using the nested <FileSet> element.

report

Generate a browsable report based on the document created by the merge.

Parameters

Attribute	Description	Required
format	The format of the generated report. Must be "noframes" or "frames".	No, default to "frames"
styledir	The directory where the stylesheets are defined. They must be conforming to the following conventions: For the noframes format, only the stylesheet overview-summary.xsl is used. For the frames format, the result will be javadoc-like. List of package will be in top left frame, the list of classes in bottom left frame and the details/summary in the main window. It uses the following XSLs: `all-packages.xsl` - creates an all-packages.html file that contains the list of all packages (top-left frame) with links to their corresponding package-summary.html files in their respective location (package name matches path name) `all-classes.xsl` - creates an all-classes.html file that contains the whole list of classes in all packages with links to their corresponding <classname>-details.html in their respective package directory. `overview-packages.xsl` - creates an overview-packages.html that makes a summary of all packages and classes not belonging to a package. `class-details.xsl` - creates a detailed page about the testcases of a testsuite. This this xsl will be applied on all testsuites and written to the <classname>-details.html file located in their respective package directory. `package-summary.xsl` - create a testsuite summary for a package. This will be written to package-summary.html in its corresponding package directory. `classes-list.xsl` - creates the list of classes belonging to a specific package. This will be written to classes-list.html in its corresponding package directory.	No. Default to embedded stylesheets.
todir	The directory where the files resulting from the transformation should be written to.	No. Default to current directory
extension	The extension of the generated files, they must include the dot (ex: .html)	No. Default to .html

Example of report

<junitreport todir="./reports">
  <fileset dir="./reports">
    <include name="TEST-*.xml"/>
  </fileset>
  <report format="frames" todir="./report/html"/>
</junitreport>

would generate a TESTS-TestSuites.xml file in the directory reports and generate the default framed report in the directory report/html.