ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: JUnit task - capturing system state with results
Date Tue, 05 Jun 2001 06:22:21 GMT
Erik Hatcher <erikhatcher@earthlink.net> wrote:

> Currently I'm grabbing these:
> 
>     Project.getUserProperties()
>     Project.getProperties()

user-properties are a subset of properties, so you might as well stick
to the later.

> Should I be capturing anything else?

Various versions: JDK, Ant, JUnit if possible, OS - see what the test
target it Ant's own build file does. All these things are properties,
but they have a special meaning and are worth to be listed separately
IMHO.

> I have (locally only, of course) modified the JUnitTask.java file to
> capture these properties and will also be modifying
> XMLJUnitResultFormatter.java file to pull these properties from the
> JUnitTest instance and put them into the XML result as well as add
> the output of these properties in XSL so that the <junitreport> tag
> will include this in the HTML results.

Maybe it would be better to add a setContext - or the like - method to
JUnitResultFormatter where you pass in all the stuff and let the
Formatters decide what they want to do with the information?

Cheers

        Stefan

Mime
View raw message