I am having multi module project and trying to generate aggregate coverage. when i check the report few classes are showing 0% coverage when i run that module separately it shows the right coverage. is there any problem with DB merge. Is there any other way to maintain order of DB merge? because i see sub modules are down in the list which has no coverage (Main module has code coverage)
i am using clover 3.1.0 and the command
mvn clean deploy clover2:instrument clover2:aggregate clover2:clover
When i run the modules separately i could see the coverage for those classes. would there be any problem with order db merge?
I am covering few tests from other modules
Ex: lets say i have 3 modules mod1, mod2 & mod3
mod 2 has 70% coverage from same module (Tests are written in the same module under /test directory) and 20% covered from mod 3 (invokes mod 2 classes).
when i run mod3 alone it shows 20% coverage of mod2 but when i build through jenkins i see clover merge order as
and coverage of that 20% is not shown. it shows as 0% covered.
is there a way to control the order of clover db merge?
If your classes are covered by tests coming from different modules db merge isn't the operation you want.
Merge will pick coverage for a class from a coverage file it first encounters (from first module it processes). So if you have more coverage for that class in another module it won't be picked up.
If you have test coverage across different modules I think you should use singleCloverDatabase option.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs