You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Hello all,
We need to prove we can measure coverage for a given project by combining coverage db from various test projects.
Our structure goes as follows:
None of this projects share a parent pom, nor can they.
This is what I've tried:
//instrument project-src-x binaries $ project-src-x: mvn clean clover:setup install //run project-it-y tests $ project-it-y: mvn clean clover:setup -Dmaven.clover.cloverDatabase=/tmp/clover-y.db //run project-ut-z tests $ project-ut-z: mvn clean clover:setup -Dmaven.clover.cloverDatabase=/tmp/clover-z.db //merge clover dbs and generate report $ project-src-x : mvn clean clover:merge -Dmaven.clover.merge.basedir=/tmp/ clover:clover
The resulting report has no information about project-src-x at all.
I know both test projects are using the instrumented code of project-src-x because I needed to include clover's jar in order to execute them.
What can be the problem here?
Thanks in advance,
$ project-src-x: mvn clean clover:setup install
Where do you write clover.db file for this project? As you run clover:merge with -Dmaven.clover.merge.basedir=/tmp, then I assume that for project-src-x you should write clover.db to /tmp as well. And the most probably you write it to standard location (<project-src-x dir>/target/clover).
Please try to run:
mvn clean clover:setup install -Dmaven.clover.cloverDatabase=/tmp/clover.db
Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.