Hi all,
we use clover for generating test coverage reports for our graph library.
<address> http://userpages.uni-koblenz.de/~ist/jgralab/coverage/report/</address><address> </address><address>We use Clover for Ant, thus our build.xml contains:</address><property name="clover.jar" value="${lib.dir}/clover/clover-3.1.0.jar" />
<taskdef resource="cloverlib.xml" classpath="${clover.jar}" />
<target name="with.clover">
<clover-setup />
</target>
<target name="clover.html">
<clover-html-report
outdir="${project.dir}/build/clover-report"
title="JGraLab Clover Report" />
</target>
To generate a new report, we just run:
ant with.clover build test clover.html
My question is: How can we exclude several classes/packages from the report generation?
For example, we don't want to have our test classes listed in the report. Currently, some non-JUnit test classes show up as top project risks, which is clearly wrong.
Likewise, we want to exclude several packages that contain only classes and interfaces generated by our code generator. The code generator is well-tested, so we may assume its output is correct and there's no need to cover everything it has generated.
You don't want to exclude test classes from your report. Really, you don't! You want to partition the reports into test code and non-test code. This way the top risks will be restricted to the non-test code.
Check out the <testsources/> element for <clover-report/> & <clover-html-report/> http://confluence.atlassian.com/display/CLOVER/clover-report#clover-report-Testsources
To filter out individual packages, try out the <fileset/> element
http://confluence.atlassian.com/display/CLOVER/clover-report#clover-report-Fileset
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi...
sorry, but how this filter works with maven?
my pom is:
<plugin>
<groupId>com.atlassian.maven.plugins</groupId>
<artifactId>maven-clover2-plugin</artifactId>
<configuration>
<excludes>
<exclude>nothing here is working, even "*.java"</exclude>
</excludes>
</configuration>
</plugin>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.