XSL Report

["Mills, Theo" <th...@twc.state.tx.us>]

I've tried searching the archives, but haven't found an answer to my issue.

In a nutshell, I'm not finding the HTML Unit Test Results report that Cactus
generates using the XSL transformation (junit-noframes.xsl) very useful.
We've got a single TestAll TestCase class that combines the suites from a
number of test classes, each with a number of test methods. However, when
the report is generated all the methods from all the classes are crammed
together in a single HTML table without any indication of which test class
they orginated in. This doesn't seem to reflect the nested test case
hiearchy that I've heard JUnit is capable of.

Is this right or am I missing something?

Thanks!

-Theo Mills

RE: XSL Report

[Vincent Massol <vm...@pivolis.com>]

Hi Theo,

Cactus has several ways of executing tests. If you use the Maven plugin
or the Ant integration, you'll find you get exactly the same report as
the junit one as our <cactus> Ant task extends the <junit> class. 

Now it seems you're referring to the servlet test runner, i.e. execution
of cactus tests from a browser. For this way of executing tests, the XML
that is generated does not yet have all the information needed to
produce reports as nice as the <junit-report> Ant task for example.

If you're interested in submitting a patch, the relevant code to improve
can be found here:

http://cvs.apache.org/viewcvs/jakarta-cactus/framework/src/java/share/or
g/apache/cactus/server/runner/XMLFormatter.java?rev=1.11&content-type=te
xt/vnd.viewcvs-markup

(the toXML() method needs to be improved)

Thus, if you wish to get the exact same report as junit, you should use
either the Ant cactus task (available only in Cactus 1.5dev - see
http://jakarta.apache.org/cactus/integration/ant/index.html) or the
Maven plugin (http://maven.apache.org/reference/plugins/cactus).

-Vincent

> -----Original Message-----
> From: Mills, Theo [mailto:theo.mills@twc.state.tx.us]
> Sent: 05 June 2003 22:27
> To: 'cactus-user@jakarta.apache.org'
> Subject: XSL Report
> 
> I've tried searching the archives, but haven't found an answer to my
> issue.
> 
> In a nutshell, I'm not finding the HTML Unit Test Results report that
> Cactus
> generates using the XSL transformation (junit-noframes.xsl) very
useful.
> We've got a single TestAll TestCase class that combines the suites
from a
> number of test classes, each with a number of test methods. However,
when
> the report is generated all the methods from all the classes are
crammed
> together in a single HTML table without any indication of which test
class
> they orginated in. This doesn't seem to reflect the nested test case
> hiearchy that I've heard JUnit is capable of.
> 
> Is this right or am I missing something?
> 
> Thanks!
> 
> -Theo Mills
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org