I am getting the following exception from NCrunch when tests are being run.
*** Failures ***
Execute
TypeMock.TypeMockException:
*** Typemock Isolator is currently disabled. Enable using the following:
* Within Visual Studio:
- Use Typemock Smart Runner
- For other runners, Choose Typemock Menu and click "Integrate with Other Runners"
* To run Typemock Isolator as part of an automated process you can:
- run tests via TMockRunner.exe command line tool
- use 'TypeMockStart' tasks for MSBuild or NAnt
For more information consult the documentation (see 'Running Unit Tests in an Automated Build')
HResult: -2146233088
at TypeMock.InterceptorsWrapper.VerifyInterceptorsIsLoaded()
at _I2KaEbJqCiZdAXHCaew5L4YgGK2_._YVpKHl6s8x54awChyHFFGG1W9p_._M9wuZsfNQUSOigKL83XBnloMATg_()
at TypeMock.MockManager.Init(Boolean collectAllCalls)
at _gpWkmvHy51MsHfP5XcTmisQFOGh_._w05d89eUlRCsAnXfWIN6HIvOW7P_._LZu54JRvjOVy0mycnVTOacyFHBR_[?](Members , Constructor , Constructor , Type , Object[] )
at _gpWkmvHy51MsHfP5XcTmisQFOGh_._w05d89eUlRCsAnXfWIN6HIvOW7P_.Instance[T](Members behavior, ConstructorWillBe constructorBehavior, BaseConstructorWillBe baseConstructorBehavior)
at NOES.Business.Control.Rollformers.RollformerStateIdleTest.SendNextBagTest() in C:\Users\Frank Adcock\Documents\noes_3\src\NOESTest\Business\Control\Rollformers\RollformerStateIdleTest.cs:line 18
Version Details
VS2015 14.0.25420.01 Update 3
Typemock 8.5.0.2
Test Framework - Galio/MbUnit or Nunit 3.43
From what I can read of the documentation Typemock is supposed to be automatically picked up by NCrunch, but this does not appear to be happening.
Any assistance welcomed
Remco NCrunch Developer
#9262
07 Oct 2016 22:06 UTC
Hi, thanks for sharing this issue.
This area of the integration is handled by TypeMock. You'll need to report this issue to them. Sorry, there isn't anything I can do from this side to help with such a problem.
This area of the integration is handled by TypeMock. You'll need to report this issue to them. Sorry, there isn't anything I can do from this side to help with such a problem.
So the advertised functionality of working with typemock is incorrect?
Remco NCrunch Developer
#9264
07 Oct 2016 23:14 UTC
TypeMock itself is a product that is under development. NCrunch works with TypeMock by invoking TypeMock's proxy process when initialising it's test environment where TypeMock has been detected. There is actually very little NCrunch does to support TypeMock in the execution environment other than making the call to initialise it.
This was done through an API that has existed in TypeMock for at least 4 years, and there have been no changes made to NCrunch's interaction with the API. So this must have happened as a result of changes made on their side of the integration point. Because the failure itself is being reported by TypeMock and NCrunch has not seen any changes to the integration, there is nothing I can do to troubleshoot it. I've referred this request to their support team.
This was done through an API that has existed in TypeMock for at least 4 years, and there have been no changes made to NCrunch's interaction with the API. So this must have happened as a result of changes made on their side of the integration point. Because the failure itself is being reported by TypeMock and NCrunch has not seen any changes to the integration, there is nothing I can do to troubleshoot it. I've referred this request to their support team.
Edited 07 Oct 2016 23:16 UTC
Remco NCrunch Developer
#9265
09 Oct 2016 22:34 UTC
I've heard back from the TypeMock developers. I'll post the details below:
We fixed the integration, but it’ll be available in our next release.
For your user you can advise add following lines in the knowRunners.dat from the Typemock installation folder:
- "nCrunch.EngineHost462.x64"
- "nCrunch.EngineHost462.x86"
You can find full info here: https://www.typemock.com/docs?book=Isolator&page=Documentation%2FHtmlDocs%2FExtendConfiguration.htm
I'll just add that the EngineHost EXEs above do depend upon the version of VS and .NET you happen to be using. The other EngineHosts may also need to be added to this file if you are using other versions of VS or you don't have .NET 4.6.2 installed:
nCrunch.EngineHost20.x64.exe
nCrunch.EngineHost20.x86.exe
nCrunch.EngineHost40.x64.exe
nCrunch.EngineHost40.x86.exe
nCrunch.EngineHost45.x64.exe
nCrunch.EngineHost45.x86.exe
nCrunch.EngineHost451.x64.exe
nCrunch.EngineHost451.x86.exe
nCrunch.EngineHost452.x64.exe
nCrunch.EngineHost452.x86.exe
nCrunch.EngineHost46.x64.exe
nCrunch.EngineHost46.x86.exe
nCrunch.EngineHost461.x64.exe
nCrunch.EngineHost461.x86.exe
We fixed the integration, but it’ll be available in our next release.
For your user you can advise add following lines in the knowRunners.dat from the Typemock installation folder:
- "nCrunch.EngineHost462.x64"
- "nCrunch.EngineHost462.x86"
You can find full info here: https://www.typemock.com/docs?book=Isolator&page=Documentation%2FHtmlDocs%2FExtendConfiguration.htm
I'll just add that the EngineHost EXEs above do depend upon the version of VS and .NET you happen to be using. The other EngineHosts may also need to be added to this file if you are using other versions of VS or you don't have .NET 4.6.2 installed:
nCrunch.EngineHost20.x64.exe
nCrunch.EngineHost20.x86.exe
nCrunch.EngineHost40.x64.exe
nCrunch.EngineHost40.x86.exe
nCrunch.EngineHost45.x64.exe
nCrunch.EngineHost45.x86.exe
nCrunch.EngineHost451.x64.exe
nCrunch.EngineHost451.x86.exe
nCrunch.EngineHost452.x64.exe
nCrunch.EngineHost452.x86.exe
nCrunch.EngineHost46.x64.exe
nCrunch.EngineHost46.x86.exe
nCrunch.EngineHost461.x64.exe
nCrunch.EngineHost461.x86.exe
Edited 09 Oct 2016 22:36 UTC
Post a reply
Log in to reply.