chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Answers. Here you can ask and receive answers from other community members. And if you liked or disliked an answer or thread: react with an up- or downvote Enjoy!
0 votes
Hello,

Our build server recently stopped generating code coverage reports (using NCover 2.1). Not sure if it was related to upgrade to TypeMock 5.1, but it happenned at about the same time. NCover fails to collect coverage data. Today I played with the server, trying to reinstall both products, running regsvr32 on NCover DLL and even tried applying "corflags 32BIT+" as it was suggested here and in NCover forum. Suddenly coverage was generated but all tests that require TypeMock failed complaining that TypeMock was not enabled. And then any attempt to enable it failed. I start TypeMock Isolator configuration tool, select "NCover 2.0" and click on "Link with TypeMock Isolator" button. Then if I restart configuration tool it still reports that they are unlinked offering to link them. And of course all unit tests with mocking fail.

Has anyone experienced this behavior? What can be done to fix it?

Thanks in advance.
asked by (19.4k points)

5 Answers

0 votes
I did more tests locally (on a different machine). I started uninstalling TypeMock and then installing a new version, downgrading until I managed to link it to NCover 2.0 and keep the link after closing TypeMock configuration. I had to go back to TypeMock 4.2.4 to succeed. Any attempts to link TypeMock 5.x versions to NCover and retain link failed.

Puzzled :roll:
answered by (19.4k points)
0 votes
Hi

Thanks for the report.
Can you please add the following details:
How do you enables Typemock Isolator? (msbuild task, TMockrunner etc...)
What is your test runner? (nunit, mstest)
answered by (35.5k points)
0 votes
Hi,

We run TypeMock using MSBuild/CruiseControl.NET, NCover 2.0 and NUnit.

But the problem seems to begin before the build starts. I simply can't link TypeMock with NCover 2.0 and keep the choice persistent. If I start TypeMock configuration, instead of "Unlink" it still shows "Link" button.

This behavior occurs both on build and my local machine. And I managed to keep link setting by downgrading to TypeMock 4.2. After upgrading back to TypeMock 5.1 (or 5.11) the problem occurs again.
answered by (19.4k points)
0 votes
Hi

Thanks for the details.
We will try to solve this issue.
I will update you as soon as we will have something.
answered by (35.5k points)
0 votes
Thanks! We're impatiently waiting :D
answered by (19.4k points)
...