From: Steven C. <ste...@re...> - 2012-01-16 10:02:36
|
I don't think there's a way to generate a subset of all the instrumented code. You might have some luck though with hudson/jenkins or sonar which can give you a probably more detailed analysis of your code. Can't you just exclude unnecessary packages from being instrumented? Exclude everything and only include foo.bar.* when instrumenting. On 1/16/2012 3:21 AM, Tomas F wrote: > Hi, > Is it possible to somehow get a code coverage summary of a subset of > packages? I have 75 packages > in my Java project that are ordered in a certain hierarchy: > > foo > foo.bar > foo.bar.x > foo.bar.y > foo.frotz.x > foo.frotz.y > > Since the number of packages is so big, It is very hard to get an > overview of the cobertura report. The only summary > I get is the summary of the whole project. This summary is of course > also valuable, but it would be great if I could tell cobertura to > create a summary of all "sub"-packages with the prefix foo.bar, given > the example above. > > Best regards, > Tomas > > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Mar 27 - Feb 2 > Save $400 by Jan. 27 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev2 > > > _______________________________________________ > Cobertura-devel mailing list > Cob...@li... > https://lists.sourceforge.net/lists/listinfo/cobertura-devel Email Disclaimer: http://www.redprairie.com/emaildisclaimer/ |