CollectFromChildProcesses supported?
See original GitHub issueWith the Microsoft CodeCoverage collector it is possible to collect code coverage from child processes via the following setting in the .runsettings file:
<CollectFromChildProcesses>True</CollectFromChildProcesses>
It this also possible with coverlet.collector?
Issue Analytics
- State:
- Created 2 years ago
- Comments:21
Top Results From Across the Web
Configure unit tests by using a .runsettings file
The run settings file for a project is specified by the property RunSettingsFilePath. Project-level run settings is currently supported in C#, ...
Read more >Customizing Code Coverage Analysis - Visual Studio
Learn how to use the ExcludeFromCodeCoverageAttribute attribute to exclude test code from coverage results. You can include assemblies ...
Read more >DataCollector enabled in VsTest task by default
In case you need answers to common questions or need assisted support, be sure to use https://visualstudio.microsoft.com/vs/support/.
Read more >runsettings.xml file not working with dotnet test coverage ...
As you can see that I specified only to include *WCController.dll assembly but still it is showing coverage of other assemblies as well....
Read more >Code Coverage - RoboKiwi.com
You can configure Code Coverage by using a .runsettings file. This is an XML configuration file, and there is no longer built-in support...
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 FreeTop 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
Top GitHub Comments
@MarcoRossignoli OK, I see. This double backslash escaping is not a problem. Instrumentation of modules also works when the directory names have double backslashes as a path separator.
I’m closing this. Thanks a lot for your support!
Happens again, created new issue #1338.