I have been trying to run tests using TestDriven .Net from within VS2005 using TypeMock 4.03. Am am also using Resharper although i doubt that has anything to do with this. I have the very latest beta of TestDriven (it was also happening with prior editions). It does not matter if the test uses TypeMock directly or not. I am linked to the latest version of ncover 1.5.8.0.
Whenever i run these nothing happens for a while then i get the following error in the output window:
Couldn't connect to test runner process
No other information is provided. Unless i remove the typemock addin i cant run any tests at all. 2nd serious issue i have found in 2 days and i can't find any mention of it anywhere. Wouldnt mind so much if this product didn't cost so much. I think this product is awsome when it works but it is a battle to make it work (and stay working). :?
The Linked profilers log contains:
Logging program: C:Program FilesTestDriven.NET 2.0ProcessInvocation.exe
Cannot read EnvName0 => The system cannot find the file specified. Reset Location: C:PROGRA~1NCoverCoverLib.dll
Adding profiler: {6287B5F9-08A1-45E7-9498-B5B2E7B02995}
Loaded C:PROGRA~1NCoverCoverLib.dll
Adding typemock profiler
Loaded C:Program FilesTypeMockTypeMock.NETMockWeaver.dll
Target Runtime .NET 2.0
Initialize Profiler 0, Target Runtime .NET 2.0
Initialize Profiler 1, Target Runtime .NET 2.0
The other log for processinvocation.exe contains:
Logging program: C:Program FilesTestDriven.NET 2.0ProcessInvocation.exe
Known namespace: nunit
Known namespace: vstesthost.exe
Known namespace: MbUnit
Known namespace: TestDriven.TestRunner.dll
Known namespace: JetBrains.ReSharper.UnitTestRunner.exe
This did work previously.