ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Hatton" <>
Subject RE: JUnitReport - more info to display?
Date Fri, 01 Nov 2002 08:49:04 GMT
I agree about what's important - but in reality, my cynicism kicks in, and the project manager
suddenly wants to see "Unit Test Reports" (like, I thought, unit testing was checking that
your code met the design at a fine-grained level, so what is there to report if it works?).

It's just that I don't see the value (to anyone other than the developer) of a list of test
methods and the word "passed" next to them. Surely you need to understand what each test case
was to get value out of such a report?


-----Original Message-----
From: Dominique Devienne []
Sent: 31 October 2002 17:41
To: 'Ant Users List'
Subject: RE: JUnitReport - more info to display?

Actually, I disagree with you. Javadocs comments of the unit test code is
always accessible, but that doesn't tell you much about what really counts,
which is how much coverage of your code is *indeed* tested.

To find out this really crucial info, use a tool like Clover. --DD

-----Original Message-----
From: Keith Hatton [] 
Sent: Thursday, October 31, 2002 11:30 AM
To: Ant-User (E-mail) (E-mail)
Subject: JUnitReport - more info to display?

Does anyone have a way of getting JUnitReport to provide more "descriptive"

I'm thinking of things like adding a JavaDoc comment to each of the test
methods and having that output in the table.
Maybe I'm looking at this the wrong way, the unit test method names may well
be descriptive to *me*, but if I want to supply the report to someone else
(for example, a PHB) it would be useful to display more information on
exactly what has been tested and I'm sure it ought to be possible to
generate this automatically.

Thanks for any ideas or solutions!

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message