Thank you for the provided info, it helps us a lot during the investigation. Here are our findings so far, I split them into two categories, it seems there is more than one issue:
Run tests without coverage
Most probably the issue was caused by the missing environment variables required of JustMock profiler, more details can be found in this documentation article. To solve this issue, just add the following variables to the build definition:
Run tests with coverage using DataCollector
This case is much complicated and it is hard to be explained in detail without referring VSTest internals. Briefly, the root cause of the issue is that JustMock configuration gets inapplicable if the code coverage is enabled via data collection outside Visual Studio, a special .runsettings is applied in this case instead. JustMock R1.2020 release delivers integration with Code Coverage for .NET Core inside Visual Studio, but some additional code changes are needed in order to have this functionality running standalone on the command line (or dotnet build task). We are going to release these changes in a service pack shortly, but until then I can provide you a custom build for testing purposes, let me know if you are interested in this option.
I hope the provided information helps. I will be glad to assist you further.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items