Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Integration Tests showing in Application Code after Clover Merge

I have two separate micro-services/application. When i run the clover report using maven command clean clover:setup verify clover:aggregate clover:clover" for each of the application individually, the report generates fine with the Integration Test included in the Test Code i.e. both *IT.java & *Test.java, and the application code properly defined in the application code.

But now when i run the clover merge using the command mvn clean clover:merge clover:clover the integrations Tests which ends with *IT.java gets included in the application code and not the Test Code. Test Code only includes *Test.java

How to fix this problem, to have integration tests *IT.java separated from application code and moved to the Test Code.

 

 <plugin>
<groupId>org.openclover</groupId>
<artifactId>clover-maven-plugin</artifactId>
<version>${clover-maven-plugin.version}</version>
<configuration>
<cloverMergeDatabase>${clover-reports-base-dir}/merge/clover.db</cloverMergeDatabase>
<baseDir>${clover-reports-base-dir}</baseDir>
<includes>**/*.db</includes>
</configuration>
</plugin>

1 answer

0 votes

If you run `mvn clean clover:merge clover:clover` the `clean` command wipes out the `target` directory. Which means that all instrumented classes and JARs as well as clover.db and recording files files are removed. 

You shall probably run sth like:

`mvn clean clover:setup verify clover:aggregate clover:clover`

or

`mvn clean clover:setup verify clover:merge clover:clover.

 

Note: the clover:aggregate goal makes basically the same as clover:merge (it merges databases into one). The only difference is that the first one searches for files based on modules executed in the maven reactor, while the second one searches for files in a given directory (and sub-directories).

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

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...

176 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you