ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephane Bailliez <sbaill...@imediation.com>
Subject [SUBMIT] Sitraka JProbe Coverage 1a/2
Date Wed, 18 Jul 2001 08:10:56 GMT
(ARGH !!! 100KB limit is hitting me hard !)

I re-submitted tasks for JProbe 2.8 a couple of weeks ago, so here is a new
shot. It fixes some bugs as well.

It might be of particular interest to QA people since I take advantage of
the XML output of JProbe 3.0 to add a new *useful* feature: a reference set.
(see covreport task description)

A reference is a set of classes whose coverage information will be checked
against. Since Coverage is only able to give you information about loaded
classes, it will only report classes that were at least used in some points
in your tests, therefore you will not be able to know what classes are not
exercised at all during your tests. The reference is an additional feature
that will analyze the bytecode of all classes in a given classpath that
match some filters and modify the XML report accordingly. In short, it will:


- remove the classes that do not exists in the reference classpath. (For
example you might have in your report some helper test classes that you do
not want to appear in the report, but are unable to filter without adding
hundred of filters for all your classes). 
- add classes that exists in the reference set and match the filters but are
not reported. 
- remove abstract methods that are incorrectly reported in JProbe 3.0
- remove classes/methods that do not match the filters. 

My best thanks to John McMillan and David AhWong from Sitraka for their
extremely responsive support and interest.

Note:
- the classes related to bytecode manipulation are not that well documented
but should be self-descriptive enough. It needs redesign as well to limit
memory usage.
- testcases are not that numerous...

Attached is (in 2 mails due to 100KB size limit):
- source code 1/2
- few testcases 2/2
- html documentation for testcases 2/2
- xsl to output the coverage report similar to the JUnit one. (see doc for
info) 2/2

-- 
 St├ęphane Bailliez 
 Software Engineer, Paris - France 
 iMediation - http://www.imediation.com 
 Disclaimer: All the opinions expressed above are mine and not those from my
company. 


Mime
View raw message