Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
MergeWith does not respect framework suffix in output file
See original GitHub issueI’m testing two binaries in my pipeline with the following (truncated) options:
dotnet test -p:CollectCoverage=true -p:CoverletOutput="../coverage.json"
dotnet test -p:CollectCoverage=true -p:MergeWith="../coverage.netcoreapp3.1.json" -p:CoverletOutput="../opencover.xml"
This produces an intermediate coverage file coverage.netcoreapp3.1.json and a final report opencover.netcoreapp3.1.json
Omitting netcoreapp3.1 in the MergeWith option value leads to a result which is not merged.
My expectation would be that the output files are either produced with the framework suffix and that the MergeWith option would respect this suffix (requiring only coverage.json as input to function properly), or that (ideally) the framework suffix is not added at all.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks, changing both .csproj files to use
TargetFrameworkinstead ofTargetFrameworkscorrected the issue. This must have been an artifact of the upgrade from 2.1 to 3.1.Feel free to close of solved!