Yes you can if you use the command line options. You need to copy over your coverage.db and all the coverage.db* files that were generated.
However if you do not have the source files on your Server A, that you did have on your Server B you are going to get a number of the following errors
ERROR: C:/Applications/Confluence_STD/Source Code/confluence-2.9-source/confluence-project/confluence/src/test/java/com/atlassian/integrationtest/confluence/core/TestConfluenceClasspath.java (No such file or directory)
The report you generate will have all the coverage statistics but when you try and drill down to the class, you will get a error stating it cannot find the source file.
If you do have the source on Server A you can specify it using the -p option from Console reporter.
How does Clover find the database at runtime?
Clover stores the path to the database file in every instrumented top-level class (inner and anonymous classes use the path from their enclosing class). This is why the database must be reachable, at that path, on the machine where the instrumented code is executed.
You can run multiple applications or application modules, using different paths to clover.db, in a single JVM.
In order to manage paths across machines, choose one of:
- copy
clover.dbto the same absolute location on each machine, - keep the database on a shared network drive,
- or instrument using relative paths and set the
clover.initstring.basedir(orclover.initstring.prefix) property at runtime, pointing to a common root folder. This is the most flexible option, and the right one when a shared drive is mounted under different absolute paths on different machines.
Once the tests have finished, the coverage recording files are written next to the database and must be copied back to the reporting machine, preserving the directory structure. See Clover JVM properties, Using Clover in various environment configurations and Working with Distributed Applications.