Feature Request / Modification Description
Description:
The current code coverage report generated by the cpp-coverage workflow in S-CORE is providing what appears to be an inaccurate and misleading view of the project's test coverage.
Current Behavior:
It has been observed that the coverage report only seems to include files that are compiled as part of a cc_test. This leads to an inflated coverage percentage, as it omits files that do not have any associated unit tests.
For example, the report shows a code coverage of approximately 80% for the lifecycle component. However, a closer look reveals that many of the .cpp files within this component do not currently have unit tests. This indicates that the report is not providing a true picture of the overall test coverage.
Requested Modification:
To ensure the coverage report is a useful and accurate tool for assessing code quality, the generation process should be modified. The report should take into account all relevant source files within the project, not just those that are part of a test compilation.
By including all files in the analysis, the report will provide a more realistic and actionable metric, helping developers to better identify areas of the code that lack sufficient testing.
Hint:
Implementation should be moved from eclipse-score/cicd-workflows#115 into this repository.
Expected Changes ot work products
Impact analysis
@RSingh1511 FYI
Safety or Security relevance
Expected required ASIL classification
QM
Expected Implementation Version (Release)
1.0
Feature Request / Modification Description
Description:
The current code coverage report generated by the cpp-coverage workflow in S-CORE is providing what appears to be an inaccurate and misleading view of the project's test coverage.
Current Behavior:
It has been observed that the coverage report only seems to include files that are compiled as part of a cc_test. This leads to an inflated coverage percentage, as it omits files that do not have any associated unit tests.
For example, the report shows a code coverage of approximately 80% for the lifecycle component. However, a closer look reveals that many of the .cpp files within this component do not currently have unit tests. This indicates that the report is not providing a true picture of the overall test coverage.
Requested Modification:
To ensure the coverage report is a useful and accurate tool for assessing code quality, the generation process should be modified. The report should take into account all relevant source files within the project, not just those that are part of a test compilation.
By including all files in the analysis, the report will provide a more realistic and actionable metric, helping developers to better identify areas of the code that lack sufficient testing.
Hint:
Implementation should be moved from eclipse-score/cicd-workflows#115 into this repository.
Expected Changes ot work products
Impact analysis
@RSingh1511 FYI
Safety or Security relevance
Expected required ASIL classification
QM
Expected Implementation Version (Release)
1.0