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
I recently updated Typemock Isolator from version 8.9.0.0 to version 9.2.3.0. Since the upgrade, none of my unit tests when run with the Resharper test runner (version 2023.2.2) and show an \"inconclusive\" result. I\'m running in Visual Studio 2019, version 16.11.27. The Isolator upgrade was the only change to my system, and before the upgrade, all tests ran as expected.

Is there a known incompatibility between Isolator 9.2.3.0 and the Resharper test runner 2023.2.2? I\'d appreciate any insight to fixing this issue. The error given by the test runner:

ERROR An exception was thrown while activating JetBrains.ReSharper.TestRunner.Implementation.TestAdapterLoadContext., reason: Autofac.Core.DependencyResolutionException: An exception was thrown while activating JetBrains.ReSharper.TestRunner.Implementation.TestAdapterLoadContext. ---> Autofac.Core.DependencyResolutionException: An exception was thrown while invoking the constructor \'Void .ctor(System.String, JetBrains.ReSharper.TestRunner.Abstractions.Objects.TestContainer, Autofac.ILifetimeScope, JetBrains.ReSharper.TestRunner.Isolation.ILoadContextTracker, JetBrains.ReSharper.TestRunner.Abstractions.ILogger)\' on type \'TestAdapterLoadContext\'. ---> System.InvalidProgramException: Common Language Runtime detected an invalid program. at JetBrains.ReSharper.TestRunner.Isolation.AssemblyLoader.IsLoggingEnabled(LoggingLevel level) at JetBrains.ReSharper.TestRunner.Isolation.AssemblyLoader.IsDebugEnabled() in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Utilities\\Isolation\\AssemblyLoader.Net35.cs:line 76 at JetBrains.ReSharper.TestRunner.Isolation.AssemblyLoader..ctor(ILogger logger) in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Utilities\\Isolation\\AssemblyLoader.Net35.cs:line 52 at JetBrains.ReSharper.TestRunner.Isolation.AssemblyLoader..ctor() in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Utilities\\Isolation\\AssemblyLoader.Net35.cs:line 33 --- End of inner exception stack trace --- at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate() at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters) at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters, Object& decoratorTarget) --- End of inner exception stack trace --- at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters, Object& decoratorTarget) at Autofac.Core.Resolving.InstanceLookup.Execute() at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters) at Autofac.Core.Resolving.ResolveOperation.ResolveComponent(IComponentRegistration registration, IEnumerable`1 parameters) at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration, IEnumerable`1 parameters) at Autofac.Core.Lifetime.LifetimeScope.ResolveComponent(IComponentRegistration registration, IEnumerable`1 parameters) at JetBrains.ReSharper.TestRunner.Extensions.AutofacExtensions.ResolveUnregistered(ILifetimeScope scope, Type serviceType, Parameter[] parameters) in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Core\\Extensions\\AutofacExtensions.cs:line 38 at JetBrains.ReSharper.TestRunner.Extensions.AutofacExtensions.ResolveUnregistered[T](ILifetimeScope scope, Parameter[] parameters) in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Core\\Extensions\\AutofacExtensions.cs:line 25 at JetBrains.ReSharper.TestRunner.Implementation.DefaultTestAdapterLoadContextFactory.Initialize(TestRequest request) in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Merged\\Implementation\\ITestAdapterLoadContextFactory.cs:line 443 at JetBrains.ReSharper.TestRunner.Adapters.NUnit3.NUnitCustomInstallationLoader.Initialize(TestRequest request) in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\Adapters\\TestRunner.Adapters.NUnit3\\NUnitCustomInstallationLoader.cs:line 46 at JetBrains.ReSharper.TestRunner.Implementation.TestAdapterLoadContextFactoryFactory.Initialize(TestRequest request) in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Merged\\Implementation\\ITestAdapterLoadContextFactory.cs:line 148 at JetBrains.ReSharper.TestRunner.Implementation.UnitTestRemoteAgent.Execute(TestRunRequest request) in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Merged\\Implementation\\UnitTestRemoteAgent.cs:line 80 at lambda_method(Closure , IAutoRegisterInProtocol ) at JetBrains.ReSharper.TestRunner.Implementation.ClientEndpoint.<>c__DisplayClass4_1.<TryRegisterHandler>b__1() in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Core\\Implementation\\ClientEndpoint.cs:line 56 at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at JetBrains.ReSharper.TestRunner.Implementation.ClientEndpoint.<RunAndLog>d__10.MoveNext() in Z:\\BuildAgent\\work\\1b668fe37ef92293\\ReSharperTestRunner\\src\\TestRunner.Core\\Implementation\\ClientEndpoint.cs:line 140
asked by calwylie (600 points)

1 Answer

0 votes

Hi,

I've opened a ticket for you in our support platform so we can investigate this issue more comfortably, check the mail you've registered with for more details. cool

answered by Erel_TypeMock (2.6k points)
...