Did you ever solve this? I have a similar problem where the coverage is not right, I have (among other modules) a service module and a dao modules. There are no tests in the dao module, but tests in the service module will excercise the daos - still the coverage is 0% for any dao classes.
onsdag 1. august 2018 10.32.22 UTC+2 skrev Marvin følgende: > > Hello Marc and a big thank you for your fast reply, > > we will go through your suggestion and keep the thread updated. > > > when exec data for the same class occurs multiple time (due to append) > it gets merged when reading the exec file. > > One thing I have not shared: We are using SQ to import the dump - Do you > maybe know about some problems reported in that direction? :) > > Best regards, > > Marvin > > Am Dienstag, 31. Juli 2018 11:27:40 UTC+2 schrieb Marc R. Hoffmann: >> >> Hi, >> >> append and merge should give the same results. When reading exec files >> for report generation all data included is merged. I.e. when exec data for >> the same class occures multiple time (due to append) it gets merged when >> reading the exec file. >> >> Some hints to identify the problem in your case: >> >> - Check your build log at what point in time the merge happens and >> when is the report generated. Maybe not everything is merged when the >> report is generated? >> - Drill down the old and new Reports for specific areas where there >> is a major difference. Maybe this gives you a clue? >> - The JaCoCo HTML report has a "Sessions" link on the top right >> corner. Here the content of the exec files is listed. >> - Alternatively you can dump the content of the exec files with our >> command line tools: See 'execinfo' command ( >> https://www.jacoco.org/jacoco/trunk/doc/cli.html) >> >> If you think the problem is with JaCoCo please create a standalone >> reproducer (preferrable GitHub repo). >> >> Regards, >> -marc >> >> >> >> On 2018-07-31 08:37, Marvin wrote: >> >> Hello together, >> >> we have a multi module Maven project and collect its coverage with the >> jacoco-maven-plugin in version 0.8.1. >> >> We configured jacoco to append the reports of all modules to a single on >> in the project root target dir: >> >> /parent >> /module-1 >> [...] >> /module-2 >> [...] >> /target >> jacoco-append.exec >> >> This works fine since years and we receive a coverage of ~70%. >> >> We now had the idea to implement some changes in our build pipeline. I >> guess the details are not important, but the result would be that we end >> up with a jacoco.exec file per module: >> >> /parent >> /module-1 >> /target >> jacoco.exec >> [...] >> /module-2 >> /target >> jacoco.exec >> [...] >> >> Based on that, we used the "merge" goal of the jacoco-maven-plugin to end >> up with one single exec file again. This again, seems to work fine too, but >> sadly, our coverage is now down to 50% without any "exclusion" / >> "inclusion" changes on our side. >> >> Has anyone an idea or a hint what could cause this? Do "append" and >> "merge" work different and is this even an expected bahavior? >> >> Thank you very much and best regards. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "JaCoCo and EclEmma Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jacoco/b95d6404-8348-4020-8764-c317c43c736f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jacoco/b95d6404-8348-4020-8764-c317c43c736f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/c442da7e-3657-4826-8d50-37363628a0a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
