ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: JUnitReport - more info to display?
Date Fri, 01 Nov 2002 15:54:18 GMT
Which is exactly the kind of info the Clover report gives you, it seems to
me: Test coverage percentages of your entire code base, further broken down
by packages and even individual classes I understand. Knowing how many test
methods you have, and their names is indeed useless, as they could be empty,
and no one (!) would know nothing was tested.

A colleague of mine wrote a very smart static analyzer of the test code to
figure out which calls it was making (by introspecting the bytecode), but
even that is not enough to figure out what really gets called at runtime,
which is necessarily a subset of the calls discovered in the bytecode (by
direct calls), and doesn't take into account the interactions of the code
tested itself. It's still a much better metric of the testing done than just
the number and names of the test methods... --DD

-----Original Message-----
From: sharon Stanfill [mailto:sharons@ll.mit.edu] 
Sent: Friday, November 01, 2002 8:11 AM
To: Ant Users List; Ant Users List
Subject: RE: JUnitReport - more info to display?

Well, actually, from an upper level management viewpoint, you shouldn't 
need to see the details, but be able to track that the testing was done.
And, at least in some areas of government work, there are various
equirements involving proving/documenting that testing was done.

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message