OpenCoverUI / OpenCover.UI

Visual Studio Integration to OpenCover
MIT License
77 stars 46 forks source link

"Cover with OpenCover" get disabled sometimes. #120

Open HarelM opened 8 years ago

HarelM commented 8 years ago

Hi,

Sometimes, not sure why, the "Cover with OpenCover" get disabled. The only workaround I found for this is to restart Visual Studio: image Note that in the above image no test execution is made. Pressing the refresh button doesn't help too.

Jacob-McKay commented 8 years ago

+1 I was able to use this tool once and it worked well, but then I ran into the option being greyed out... clean and rebuild did not help.

Restarting visual studio lets me run the tool again, but I'm still looking for a less painful solution

pver commented 8 years ago

This is a hard one, because I also notice it once in a while, but mostly not. So it's not easy to debug this. I'll add more logging on the enabling/disabling of the button

Jacob-McKay commented 8 years ago

Been using this extension for days now and haven't seen it again. Heisenbug

neoaisac commented 8 years ago

Using the latest github-built version (built it from code myself) and it still keeps on happening.

Gh0stWalk3r commented 8 years ago

I can reproduce the issue without a problem when I build the projects with ReSharper Build & Run. OpenCover.UI is always disable after I tried to start it once.

Maybe ReSharper Build & Run uses a different event to tell VS that the build has finished.

lorenh commented 8 years ago

I also see this with build of latest version (do not have ReSharper at all)

jadaml commented 7 years ago

Side note: Breakpoint over all code point where it is set to disabled? This may not be usefull though... :(

Occationally after I have run OpenCover I am running all unit test with Visual Studio to see if they pass and usually (for me it was always so far) after that it becomes disabled.

Once it happened when OpenCover UI completes while tests are selected, but wasn't able to reproduce it that way.

Edit: Now it remained enabled eventhough I have run the tests with Visual Studio.

satish049 commented 6 years ago

I was able to use it when I change the Reshaper build to VS build. As @gregor4005 mentioned it is using the VS build event to trigger the coverage.

So as a Temporary Fix, Change the build to "VS build" whenever you use the extension.