csdl.jblanket.report

The raw JBlanket results stored in XML files are aggregated into one file according to class and type of method (constructor, oneline, tested, or untested methods). This file is then parsed and formatted into HTML web pages using XSLT. Because test cases are implemented using JUnit, the report from JBlanket is formatted using a stylesheet similar to the one used by JUnit (from Apache Ant).

First this class combines all methods in the system into one XML file, 'COVER-MethodSets.xml', according to the following types:

'constructor' - constructors.
'oneline' - methods that contain only one line of code.
'excludedindividual' - excluded methods chose though ExcludedIndividualMethodsApp.
'tested' - methods invoked during testing that are not 'oneline' methods.
'untested' - methods not invoked during testing that are not 'oneline' methods.

Then the aggregate XML file can be transformed into HTML pages, mimicking the behavior found in Apache Ant's junitreport task.

Note that the excluded individual methods take priority over all the other categories of methods.

This is the last step in JBlanket.

There are two main functions of this class:

• Combines the methods invoked during testing in "COVER-*.xml" files into one XML file, where * is the fully qualified name of the test class, then derives the methods that were not tested.
• Calls the AggregateTransformer class to combine JBlanket output and transform them into HTML files.

The above mentioned functions are achieved by invoking the main method.

If using Ant to execute this test class a 'jblanket.testdir' system property needs to be set in the build.xml file.