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 Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
Last week I wrote a post about problems with TypeMock on our build server. It looked that I managed to fix the problem by disabling and re-enabling TypeMock from Visual Studio IDE. Apparently not - problem happens again and again.

Here is our environment:
MsBuild for command-line builds
VS IDE for interactive sessions
NCover for code coverage
TestDriver.NET 2.0
NMock 3.60

Using TypeMock from command line always works fine.
When I start VS IDE however, if I try to run a test using TestDriven.NET, the system just waits for minute or two and then prints in Output window that 0 tests run. If I disable TypeMock in VS, everything works fine as long as tests don't use TypeMock.

Here what TypeMock writes in log files:

Log 1:
Logging program: C:\Program Files\TestDriven.NET 2.0\ProcessInvocation.exe
Cannot read EnvName0 => The system cannot find the file specified.

Reset Location: C:\PROGRA~1\NCover\CoverLib.dll
Adding profiler: {6287B5F9-08A1-45E7-9498-B5B2E7B02995}
Loaded C:\PROGRA~1\NCover\CoverLib.dll
Adding typemock profiler
Loaded C:\Program Files\TypeMock\TypeMock.NET\MockWeaver.dll
Target Runtime .NET 2.0
Initialize Profiler 0, Target Runtime .NET 2.0
Initialize Profiler 1, Target Runtime .NET 2.0

Log2:

Logging program: C:\Program Files\TestDriven.NET 2.0\ProcessInvocation.exe
Known namespace: nunit
Known namespace: vstesthost.exe
Known namespace: MbUnit
Known namespace: TestDriven.TestRunner.dll

Any help is appreciated

Vagif
asked by vagif (19.4k points)

2 Answers

0 votes
Hi
You have two solutions to your problem:
Get the latest beta of TestDriven which links you automatically with NCover.
The other option is:
1. Disable TypeMock
2. Link with NCover.
3. Make sure you kill TestDriven. (stop the rocket)
4. Run your tests.
answered by ohad (35.5k points)
0 votes
I see. I noticed that it has something to do with NCover link. I'll try with latest TestDriven version.

Thanks for the info.
answered by vagif (19.4k points)
...