Dominique Devienne wrote:
Although Clover has the disdvantage that it requires pre-instrumentation of your code, in contrast to something JProbe Coverage which does runtime instrumentation.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
Ciao,
Gordon
--
Gordon Tyler
Software Developer, R&D
Sitraka -- Performance is Mission Critical
--
To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@;jakarta.apache.org>
