if i use dotcover from command line the coverage of the code that runs within the dotcover process as well as the code of spawned child processes will be covered. That's great!
But if i use dotcover from inside Visual Studio and cover e.g. the same unit test only the code that runs within the dotcover process will be covered. The code of spawned child processes will be ignored.
Is that right? Why?
Is there a possiblity to influence this behaviour e.g. by some configuration setting etc.?
Thanks a lot.
Results should be the same in both approaches.
As a standart check please make sure that the code of spawned child was compiled with PDBs and not filtered out with coverage filters.
Also we need dotCover log - please launch VS with the the following command-line key: /dotCover.LogFile path_to_the_log_file
Thanks in advance.
I'm sorry, I was wrong. I can confirm that currently we have an issue with coverage of child processes from VS.
Here's a corresponding report in our YouTrack: http://youtrack.jetbrains.com/issue/DCVR-6819
You are welcome to track its status.