Closed Kirdock closed 11 months ago
After thinking about the current implementation of the merge I must admit, that I don't know if such a merging generally can be done in my post processing step. I do not have enough information in the XML files to compute the coverage in the same way as a coverage tool can do.
Maybe if makes sense to cut of the coverage information at the file level and aggregate all values in the parent levels (packages, modules) on my own. I even do not show the coverages at method or class level yet.
Jenkins and plugins versions report
Jenkins: 2.401.2 code-coverage-api: 4.7.0 git-forensics: 2.0.0
What Operating System are you using (both controller, and any agents involved in the problem)?
Linux
Reproduction steps
Folder structure
/app
/shared
/app
accesses a function in/shared
, which is also tested in/shared
.app
should not test the whole function inshared
, andshared
should test more of the function thanapp
.app
are taken.shared
is taken beforeapp
app
toshared
(and the shared report is taken before the app one)shared
Expected Results
Not only the coverages should be merged, but also the files/functions. If a file/function is present in two coverage reports, the function coverage should be merged
Actual Results
One report overrides the coverage of a function of another one
Anything else?
Coverage report of app and shared while dateUtils.ts is inside app
app
```xmlshared
```xmlCoverage report of app and shared while dateUtils.ts is inside shared
app
```xmlshared
```xml