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
0 votes
When I run the tests under TypeMockRunner.exe & NUnit.exe, I get the following exception when running using the NUnitProject. When opening the assembly by itself, I do NOT get this exception. There seems to be an issue when the Test Assembly runs outside the NUnit Process. NO matter what option is selected, every time you run NUnit using the Project File, you get the exception below. Again, running the dll's directly does not give this exception.

Has anyone encountered this issue?
and resolved it???

Visual Studio 2008
.NET Framework 3.5
TypeMock 4.2.3
NUnit 2.5

Aspects.UnitTests.TraceAspectTests.ErrorLoggingAttributePositive:
TearDown : System.Reflection.TargetInvocationException : Exception has been thrown by the target of an invocation.
  ----> TypeMock.VerifyException : 
TypeMock Verification: Method Microsoft.Practices.EnterpriseLibrary.Logging.Logger.Write() has 3 more expected calls

--TearDown
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at NUnit.Core.TestMethod.doTearDown(TestResult testResult)
--VerifyException
at TypeMock.MockManager.Verify()
at RelayHealth.Utility.BaseTest.Finish() in C:Builds	runkRelayHealthdevFrameworksrcUtilityBaseTest.cs:line 36
asked by rodneykam (600 points)

1 Answer

0 votes
Hi,

NUnit 2.5 is supported starting Isolator version 5.3.1. I would strongly recommend the upgrade regardless, as there are a ton of new features, better API and a lot of bug fixes since the version you are using.

Thanks,
Doron
Typemock Support
answered by doron (17.2k points)
...