2 Replies Last post: May 21, 2014 6:32 PM by Fedor Buyvol-Kot  
Carsten Sponsel Newbie 11 posts since
Jun 30, 2011
Currently Being Moderated

May 16, 2014 4:21 PM

Coverage of child processes

Hi,

 

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.

Carsten

Fedor Buyvol-Kot JetBrains 94 posts since
Dec 9, 2011
Currently Being Moderated
May 21, 2014 5:22 PM in response to: Carsten Sponsel
Re: Coverage of child processes

Hi Carsten,

 

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.

Fedor Buyvol-Kot JetBrains 94 posts since
Dec 9, 2011
Currently Being Moderated
May 21, 2014 6:32 PM in response to: Carsten Sponsel
Re: Coverage of child processes

Hi Carsten,

 

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.

 

Best regards,

Fedor.

More Like This

  • Retrieving data ...