Skip to content

Coverage file having complete build path in it for files causing issue while merging multiple coverage files together #197

@nidhipandya030

Description

@nidhipandya030

Hi Steve,

In our environment we are generating Cobertura coverage files using AltCover on multiple testing servers.

We have dotnet based service which builds on the automation servers having distinct paths and then those services are used by testing servers.

The service for which we are generating the coverage gives the complete path of file where it was build in coverage file. Please find the example of two server's having same file with different path in Cobertura coverage file for the respective servers.

Screenshot 2023-11-15 120939

Screenshot 2023-11-15 120839

When I am merging this two Cobertura coverage files, the issue is that there are two occurrences for the same file in the merged coverage file.

Source contains two entries for same package when combined. Ex. - ServiceSource\Service\VersionControl\AdapterComponents and others.
Screenshot 2023-11-15 120602

For the above stated scenario, is there any solution to get package path for file in-place of a complete build path in coverage file for the service being tested?

Also, if you can suggest a proper way or command to merge Cobertura coverage files is such a way that only one occurrence of file is there in merged file would be helpful.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions