question-mark
Stuck on an issue?

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" option doesn't seem to be working for me

See original GitHub issue

I’m testing coverlet and it seems the “MergeWith” option does not work for me. Here’s my setup:

I created a sample solution which contains 4 .Net Core projects: Module1, Module2, Test1, Test2. Test1 tests some method in module1 and test2 tests some method in module2. Then I run command: dotnet test Test1.csproj /p:CollectCoverage=true it builds the test, run it, and generate a coverage.json file which contains the coverage summary for Module1. Everything is good. The same for Test2. However when running test2 like this: dotnet test Test2.csproj /p:CollectCoverage=true /p:MergeWith='C:\TestCoverlet\Test1\Test1\coverage.json'

The json file generated is identical with the one generated without the “MergeWith” option (only has the code coverage summary for Module2, but no Module1). It seems the option is not taking effect. Did I miss anything? It seems others didn’t encounter this issue. I have double checked the file path and made sure the file exists. I also tried using a non-exist file path, it didn’t throw any error. This isn’t normal, is it?

Packages I used in test1 and test2: <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.9.0" /> <PackageReference Include="MSTest.TestAdapter" Version="1.4.0" /> <PackageReference Include="MSTest.TestFramework" Version="1.4.0" /> <PackageReference Include="coverlet.msbuild" Version="2.5.1" />

dotnet core version is 2.1.403

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
pape77commented, Feb 12, 2019

@xiaofma I use the output param. Like this

dotnet test Test1.csproj /p:CollectCoverage=true /p:CoverletOutput="/Users/dpaz/Desktop/Test/coverage"
dotnet test Test2.csproj /p:CollectCoverage=true /p:CoverletOutput="/Users/dpaz/Desktop/Test/coverage" /p:MergeWith="/Users/dpaz/Desktop/Test/coverage.json"
0reactions
pape77commented, Feb 13, 2019

@xiaofma No problem 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

"MergeWith" option doesn't seem to be working for me #339
I'm testing coverlet and it seems the "MergeWith" option does not work for me. Here's my setup: I created a sample solution which...
Read more >
VSCode merge conflict options not displaying
I am working on an application in which I have merged my code to the repository after taking the git pull.The problem is...
Read more >
Merged with does not always work - Bugs - Bubble Forum
I'm using merged with to get a limited list of items and append another list of items. The way I structured it, the...
Read more >
Confluence: Merge function in tables does not work
I'm trying to create a table and I need to merge cells from 3 rows on top of eachother but apparently the built-in...
Read more >
Can't merge table cells - Merge Cells button "greyed out"
When I select the 2 cells, the Merge Cells button on the Table Tools Layout tab becomes unavailable or "greyed out". It doesn't...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found