Now we are at 75% in SonarCloud as well: https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-resourcemerger&metric=coverage&view=list <https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-resourcemerger&metric=coverage&view=list> Thanks again for the pointer, Konrad
> On 10. Mar 2021, at 11:27, Konrad Windszus <[email protected]> wrote: > > HI Radu, > thanks for that hint. > Most of the coverage comes from > MergedResourceProviderTestForSearchPathBasedPicker. > That is just not executed by Maven Surefire because it is not compliant with > the naming pattern > (https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#includes). > If you execute those tests manually in Eclipse or IntelliJ you obviously > reach a higher coverage ratio... > > Konrad > > >> On 10. Mar 2021, at 11:20, Radu Cotescu <[email protected]> wrote: >> >> Hi Konrad, >> >> For what it’s worth I do get a 2% line coverage for >> org.apache.sling.resourcemerger.impl.CRUDMergingResourceProvider when >> running >> org.apache.sling.resourcemerger.impl.CommonMergedResourceProviderTest in >> IntelliJ. Same when I run mvn clean verify -Pjacoco-report. >> >> Regards, >> Radu >> >
