Hi.
I cannot seem to find a way to clear current coverage without deleting NCrunch cache directory and restart vstudio, isn't that possible?
Background: I had x tests under a fixture class, including static one-time initializations, and I wanted to only see coverage from 1 test from that fixture. Filtering on coverage for fixture itself included other tests in earlier test executions so wanted to "clear everything" and only run that specific test.
Thanks.
Remco NCrunch Developer
#14413
31 Jan 2020 23:43 UTC
Hi, thanks for posting.
We don't have any feature built in that can specifically do this right now. The closest thing I can think of would be to turn off the 'Instrument output assembly' setting at a solution level, wait for the engine to reset, then turn it back on again.
We don't have any feature built in that can specifically do this right now. The closest thing I can think of would be to turn off the 'Instrument output assembly' setting at a solution level, wait for the engine to reset, then turn it back on again.
It seems to have worked out fine, but.. After toggling the "Instrument output assembly" option at solution level, the starting point indicator of tests do not seem to re-appear, not even after I run the tests and I can no longer use shortcut "pin covering tests to test window" (it executes it seems but does not pin the test), so I had to restart vstudio anyhow.
[img=https://i.imgur.com/mQ9CUjw.png]Screenshot[/img]
[img=https://i.imgur.com/Muboa7x.png]screenshot2[/img]
[img=https://i.imgur.com/mQ9CUjw.png]Screenshot[/img]
[img=https://i.imgur.com/Muboa7x.png]screenshot2[/img]
Edited 02 Feb 2020 07:24 UTC
Remco NCrunch Developer
#14419
02 Feb 2020 10:18 UTC
GreenMoose wrote:It seems to have worked out fine, but.. After toggling the "Instrument output assembly" option at solution level, the starting point indicator of tests do not seem to re-appear, not even after I run the tests and I can no longer use shortcut "pin covering tests to test window" (it executes it seems but does not pin the test), so I had to restart vstudio anyhow.
Seems like a bug to me. I'll take a deeper look at this. Thanks for letting me know.
Post a reply
Log in to reply.