-
Type:
Suggestion
-
Resolution: Handled by Support
-
Component/s: Reporting
-
Environment:JDK 1.6, Maven 3.0.2, Clover 3.1.0, Platform - Linux, Server - tomcat
Hi Everyone,
We have a multi-module project setup which we are trying to integrate with clover. The clover coverage and the reports look good. Our unit tests are written in TestNG and the integration tests are in a wrapper framework of TestNG. The problem we are facing right now is that we are seeing a broken link like $testMethod.qualifiedName for the integration test classes. We found that an external descriptor can be configured for detecting advanced test cases like this. But couldn't find much documentation on this.
We configured an external descriptor as follows
<project name="Clover Report">
<clover-setup>
<testsources dir="src/test/java">
<testclass>
<testmethod name="runTest*"/>
</testclass>
</testsources>
</clover-setup>
<target name="current">
<clover-report>
<current outfile="clover_html" title="My Project" summary="true">
<format type="html"/>
</current>
</clover-report>
</target>
</project>
And we pointed to this xml file using the command line argument -Dmaven.clover.reportDescriptor
We get an exception like this
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-clover2-plugin:3.1.0:clover (test) on project myprojectname: Execution test of goal com.atlassian.maven.plugins:maven-clover2-plugin:3.1.0:clover failed: com.atlassian.clover.registry.NoSuchRegistryException: Clover registry file "/myprojectname/.clover/clover3_1_0.db" does not exist, cannot be read or is a directory.
And the build fails.
Can anyone please provide some insight on how to configure an external descriptor file properly and also how to configure the advanced test cases with some examples.
Thanks !