[
https://issues.apache.org/jira/browse/CALCITE-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stamatis Zampetakis resolved CALCITE-5475.
------------------------------------------
Fix Version/s: 1.33.0
Resolution: Fixed
Fixed in
https://github.com/apache/calcite/commit/fe821caaa5db0050bfa6f01a8c0397a20973138f.
> Improve test coverage accuracy by aggregating modules
> -----------------------------------------------------
>
> Key: CALCITE-5475
> URL: https://issues.apache.org/jira/browse/CALCITE-5475
> Project: Calcite
> Issue Type: Task
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.33.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently the test coverage report is computed per module (using
> jacocoTestReport task) and upload it to Sonar as is. Considering the modules
> in isolation leads to some modules have rather low coverage.
> +Example+
> For testkit module, Sonar reports only 11% coverage at the moment of
> submitting this ticket:
> [https://sonarcloud.io/component_measures?metric=coverage&selected=apache_calcite%3Atestkit%2Fsrc%2Fmain&id=apache_calcite]
> Some classes such as
> [SqlOperatorTest|https://sonarcloud.io/component_measures?metric=coverage&selected=apache_calcite%3Atestkit%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fcalcite%2Ftest%2FSqlOperatorTest.java&id=apache_calcite]
> are as low as 1%.
> The testkit module does not have itself many tests covering its own classes
> (under src/main) so if we don't consider how it is used by other modules we
> get the false impression that it is not sufficiently covered.
> The test coverage accuracy can be improved by aggregating the results from
> all modules together using the
> [jacoco_report_aggregation_plugin|https://docs.gradle.org/current/userguide/jacoco_report_aggregation_plugin.html#jacoco_report_aggregation_plugin].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
