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.
Zero coverage in .net core 3 when using MassTransit
See original GitHub issueI installed .net sdk 3.0.100, now I have zero coverage if I include MassTransit. My system:
coverlet --version
Cross platform .NET Core code coverage tool
1.6.0.0
dotnet --info
.NET Core SDK (reflecting any global.json):
Version: 3.0.100
Commit: 04339c3a26
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18362
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.0.100\
Host (useful for support):
Version: 3.0.0
Commit: 7d57652f33
.NET Core SDKs installed:
2.2.402 [C:\Program Files\dotnet\sdk]
3.0.100 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Here is a sample with reproducible bug: https://gitlab.com/ittennull/coverletdemo There is one test:
[Fact]
public void Test1()
{
var service = new Service();
//comment out next line to get some coverage
service.StartMassTransit();
service.Foo(true);
service.Foo(false);
}
If I build the solution and run it like this:
coverlet .\CoverletDemo.Test\bin\Debug\netcoreapp3.0\CoverletDemo.Test.dll --target "dotnet" --targetargs "test CoverletDemo.Test\CoverletDemo.Test.csproj --no-build"
Test run for C:\tmp\CoverletDemo\CoverletDemo.Test\bin\Debug\netcoreapp3.0\CoverletDemo.Test.dll(.NETCoreApp,Version=v3.0)
Microsoft (R) Test Execution Command Line Tool Version 16.3.0
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
10
Test Run Successful.
Total tests: 1
Passed: 1
Total time: 2,1295 Seconds
Calculating coverage result...
Generating report 'C:\tmp\CoverletDemo\coverage.json'
+--------------+------+--------+--------+
| Module | Line | Branch | Method |
+--------------+------+--------+--------+
| CoverletDemo | 0% | 0% | 0% |
+--------------+------+--------+--------+
+---------+------+--------+--------+
| | Line | Branch | Method |
+---------+------+--------+--------+
| Total | 0% | 0% | 0% |
+---------+------+--------+--------+
| Average | 0% | 0% | 0% |
+---------+------+--------+--------+
If I comment out service.StartMassTransit(); then
coverlet .\CoverletDemo.Test\bin\Debug\netcoreapp3.0\CoverletDemo.Test.dll --target "dotnet" --targetargs "test CoverletDemo.Test\CoverletDemo.Test.csproj --no-build"
Test run for C:\tmp\CoverletDemo\CoverletDemo.Test\bin\Debug\netcoreapp3.0\CoverletDemo.Test.dll(.NETCoreApp,Version=v3.0)
Microsoft (R) Test Execution Command Line Tool Version 16.3.0
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
10
Test Run Successful.
Total tests: 1
Passed: 1
Total time: 1,4602 Seconds
Calculating coverage result...
Generating report 'C:\tmp\CoverletDemo\coverage.json'
+--------------+--------+--------+--------+
| Module | Line | Branch | Method |
+--------------+--------+--------+--------+
| CoverletDemo | 27,77% | 20% | 33,33% |
+--------------+--------+--------+--------+
+---------+--------+--------+--------+
| | Line | Branch | Method |
+---------+--------+--------+--------+
| Total | 27,77% | 20% | 33,33% |
+---------+--------+--------+--------+
| Average | 27,77% | 20% | 33,33% |
+---------+--------+--------+--------+
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7
Top Results From Across the Web
Zero coverage in .net core 3 when using MassTransit #573
I installed .net sdk 3.0.100, now I have zero coverage if I include MassTransit. My system: coverlet --version Cross platform .NET Core code ......
Read more >Using MassTransit with RabbitMQ in ASP.NET Core
In this article, we are going to take a look at how we can use the open-source, distributed application library MassTransit in conjunction ......
Read more >How to use MassTransit in .NET Core with RabbitMQ
Learn how to implement MassTransit with RabbitMQ in .NET Core. this tutorial will teach how to work with queues and exchanges in RabbitMQ....
Read more >MassTransit and .NET Core DI - how to resolve ...
I am working on the app using .NET Core 2 and MassTransit 4(dev). Mass Transit requires parameterless constructor for consumers.
Read more >Use code coverage for unit testing - .NET
Code coverage is a measurement of the amount of code that is run by unit tests - either lines, branches, or methods. As...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ittennull I found the issue. It’s a know issue of interaction between vstest and exit process. To solve you have to use “collectors” and not dotnet tool. Again during debug I found also a possible bug on vstest platform(dotnet test) so you need to pass a custom “runsetting” file. Try with this:
And use integrated collector https://github.com/tonerdo/coverlet#vstest-integration
On my local will be generated a valid cobertura file with hit on lines
Unfortunately using collector we cannot show percentage so you need to use some tool like report generator.
TL;DR;
You have to use collector because when test is end rabbitMQ is slow to “close” this lead vstest plat to “kill” process. For msbuild and dotnet tool we use a pair of AppDomain event to trigger hit file flush(where we collect hits). But vstest by design after some time kill host process if pending and so we cannot flush file to disk. No file result in 0% of coverage. With collector we’re integrated to vstest so there is a communication between testhost and vstest, vstest doesn’t close host process until we flush file.
@fkucuk I think that this is the reason also for your issue…you should try this way.
Thanks, I managed to get it work as needed