offset123 wrote:
My point was that both of these tests are _already_ pinned and the coverage should be updated automatically for both of them. Subsequently, when I changed the code, both were run and coverage was updated. So there seems to be some kind of malfunction (this wasn't happening in v3.3 and before).
Is this something you can reproduce consistently? If so, I may be able to look at it in more detail if you can provide me with a means to produce it.
Remco wrote:
Is this something you can reproduce consistently? If so, I may be able to look at it in more detail if you can provide me with a means to produce it.
I don't know - frankly there are several problems with the new NCrunch and I can't really distinguish between one case and the other, I just notice general instability. And I've downgraded NCrunch to v3.3 on the VS 2015 installation on my main dev machine, so I probably won't be able to detect this again, unless it occurs on other 3 VS installations or if it happens on the old version, too.