Not able to get code coverage of integration test

[Shankar KC]

Hi We are evaluating to use clover for one of our product. We have a lot of legacy seleniumIDE tests and we want to leverage on clover to perform test optimization. When I run the integration tests clover shows "No classes were hit by this test." I am not sure what am i missing here. Can you pls help. Here is the corgo plugin section from my pom file.

Here is link to my POM XML :- https://onedrive.live.com/redir?resid=C04D20DC7384222A%212014 

Here is the log file :- https://onedrive.live.com/redir?resid=C04D20DC7384222A%212057

Though I have specified <clover.distributed.coverage>host=localhost;port=7777;numclients=1</clover.distributed.coverage> I see in log 

Distributed coverage is enabled with: name=clover.tcp.server;host=localhost;port=1198;timeout=5000;numClients=0;retryPeriod=1000
Starting distributed coverage service.

I know its some configuration issue. But I am not sure what is missing here.

I am running the tests as below :-

mvn -Dclover.server=true  clover2:clean clover2:setup clover2:optimize install  clover2:log  clover2:aggregate clover2:clover clover2:snapshot

<plugin>
				<groupId>org.codehaus.cargo</groupId>
				<artifactId>cargo-maven2-plugin</artifactId>
				<version>1.2.0</version>
				<configuration>

					<!-- Container configuration -->
					<container>
						<containerId>tomcat6x</containerId>
						<type>remote</type>
						<dependencies>
							<!-- We need clover.jar to be present in container classpath -->
							<dependency>
								<groupId>com.cenqua.clover</groupId>
								<artifactId>clover</artifactId>
							</dependency>
						</dependencies>
					</container>
					<systemProperties>
						<clover.distributed.coverage>ON</clover.distributed.coverage>
		<clover.distributed.coverage>host=localhost;port=7777;numclients=1</clover.distributed.coverage>
					</systemProperties>
					<!-- Configuration to use with the Container -->
					<configuration>
						<type>runtime</type>
						<properties>				<cargo.tomcat.manager.url>http://localhost:8080/manager</cargo.tomcat.manager.url>
							<cargo.remote.username>deployer</cargo.remote.username>
							<cargo.remote.password>deployer</cargo.remote.password>
						</properties>
					</configuration>
					<!-- Deployer configuration -->
					<deployer>
						<type>remote</type>
						<deployables>
							<deployable>
								<groupId>${project.groupId}</groupId>
								<artifactId>${project.artifactId}</artifactId>
								<type>war</type>
							</deployable>
						</deployables>
					</deployer>
				</configuration>
				<executions>
					<execution>
						<id>deploy</id>
						<phase>pre-integration-test</phase>
						<goals>
							<goal>redeploy</goal>
						</goals>
						<configuration>
							<type>runtime</type>
							<properties>
			<cargo.tomcat.manager.url>http://localhost:8080/manager</cargo.tomcat.manager.url>
								<cargo.remote.username>deployer</cargo.remote.username>
								<cargo.remote.password>deployer</cargo.remote.password>
							</properties>
						</configuration>
					</execution>
				</executions>
			</plugin>

[Marek Parfianowicz]

Hi Shankar,

Coming back to your question:

When I run the integration tests Clover shows "No classes were hit by this test." I am not sure what am i missing here.

There are few possible reasons of this.

1) First of all - do you see any code coverage for your application when you run integration tests? I'm asking about the global coverage, not the per-test coverage. If there's no global coverage then it may be caused by a fact that application instrumented by Clover was unable to locate clover.db file. If this happens, you should see a proper error message in application's log, such as:

"CLOVER: Unable to load the coverage database at <path>"
"CLOVER: No coverage data will be gathered."

I suspect that you may have this problem. Could you check your logs, please?

I've found that in maven-surefire-plugin you're passing location of the Clover database in a wrong way:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>2.17</version>
  <configuration>
    <cloverDatabase>/Users/i306565/.clover/clover.db</cloverDatabase>
  </configuration>
</plugin>

Surefire does not have the <cloverDatabase> configuration option. Therefore, if you need to pass this path, you have to use a property. However, the most probably you don't need this property here at all (sic!). It's because tests are being launched from the same working directory as the build  is performed. Thus, there shall be no problem with locating the database.

However, as you're using Cargo plugin to run your application, you may need to pass this property here:

<plugin>
  <groupId>org.codehaus.cargo</groupId>
  <artifactId>cargo-maven2-plugin</artifactId>
  <version>1.2.0</version>
  <configuration>
    <clover.initstring>/Users/i306565/.clover/clover.db</clover.initstring>
    ...
  </configuration>
</plugin>

2) If you already see global coverage for both application and integration tests, it may happen that you will see no per-test coverage in an HTML report. Could you please open such report and check if any of your integration tests have some application classes covered?

If not, then the most probably distributed coverage did not start properly - please note test execution must not start before "Clover clients" are connected to the "Clover server".

I've found the following messages in your build log:

Running com.ariba.demo.ITSeleniumIDETests
Distributed coverage is enabled with: name=clover.tcp.server;host=localhost;port=1198;timeout=5000;numClients=0;retryPeriod=1000
Starting distributed coverage service.

As you can see, "Clover server" started immediately, without waiting for any clients (numClients=0). I don't know what happened on application side, however - could you share an application log too, please?

The most probably you shall use:

<clover.distributed.coverage>numclients=1</clover.distributed.coverage>

in maven-cargo-plugin; but I have to see logs first to be certain.

And what about problem with test optimization?

In my opinion, as soon as you have per-test coverage for integration tests recorded correctly, test optimization will start working as expected.

Cheers
Marek

[Marek Parfianowicz]

Hi Shankar,

1) In the pom.xml, in maven-clover2-plugin configuration section you have an empty tag:

<distributedCoverage />

Please do one of the following:

• remove this tag or
• use "<distributedCoverage>ON</distributedCoverage>" or
• use properties in this tag, for instance "<distributedCoverage>host=localhost;numClients=1</distributedCoverage>"

2) In the pom.xml, in maven-surefire-plugin configuration section you have:

<property>
  <name>clover.distributed.coverage</name>
  <value>ON</value>
</property>

This setting is required only if the <distributedCoverage> has not been set during compilation (in the maven-clover2-plugin). Thus, depending on an action you'll choose in point 1), you may need to remove it.

3) In the pom.xml, in cargo-maven2-plugin you have:

<systemProperties>
  <clover.distributed.coverage>ON</clover.distributed.coverage>
  <clover.distributed.coverage>host=localhost;port=7777;numclients=1</clover.distributed.coverage>
</systemProperties>

It's not possible to pass the same property twice. The latter one is ignored. Thus, please use only one of them.

4) You wrote that you've used a command as follows:

mvn -Dclover.server=true  clover2:clean clover2:setup clover2:optimize 
install  clover2:log  clover2:aggregate clover2:clover clover2:snapshot

In my opinion -Dclover.server=true is obsolete here, because it's already present in maven-surefire-plugin's configuration.

You may also reconsider whether it's necessary to run "install" phase - please note that this causes that JARs containing instrumented code will be installed to ~/.m2. The most probably running "test" or "verify" should be sufficient.

Cheers
Marek