Unable to access test execution dependent service 'Reqnroll.ScenarioContext' with the Reqnroll.Microsoft.Extensions.DependencyInjection plugin

[iarsova]

Hey.
I have replaced Specflow with Reqnroll but now all of the tests are failing with this:

Unable to access test execution dependent service 'Reqnroll.ScenarioContext' with the Reqnroll.Microsoft.Extensions.DependencyInjection plugin. This service is only available once test execution has been started and cannot be used in '[BeforeTestRun]' hook.

I don't have BeforeTestRun, neither I have AfterTestRun, neither I am using Parallel execution.

Can someone please help me resolve this problem? I have searched everywhere and tried everything.

Thanks in advance

[clrudolphi]

What other hooks do you have in your solution? This error could fire when ever there is an attempt to access the ScenarioContext when it is not available (such as Before/AfterTestRun and Before/AfterFeature).

Can you provide the full stack-trace when this error occurs?

Can you share your ScenarioDependencies setup method?

[iarsova]

Thank you for your answer.

I would like to share that I am trying to migrate from Specflow to Reqnroll.
I didn't have any issues with Specflow, but now with Reqnroll I have this one:

This is the only stack trace I have:

Message: 
Reqnroll.ReqnrollException : Unable to access test execution dependent service 'Reqnroll.ScenarioContext' with the Reqnroll.Microsoft.Extensions.DependencyInjection plugin. This service is only available once test execution has been started and cannot be used in '[BeforeTestRun]' hook. See https://go.reqnroll.net/doc-migrate-specflow-testrun-hooks for details.
TearDown : Reqnroll.ReqnrollException : Unable to access test execution dependent service 'Reqnroll.ScenarioContext' with the Reqnroll.Microsoft.Extensions.DependencyInjection plugin. This service is only available once test execution has been started and cannot be used in '[BeforeTestRun]' hook. See https://go.reqnroll.net/doc-migrate-specflow-testrun-hooks for details.

Stack Trace: 

DependencyInjectionPlugin.<RegisterProxyBindings>g__GetTestThreadDependency|9_17[TResult](IServiceProvider sp, Func`2 selector)
<>c.<RegisterProxyBindings>b__9_21(IServiceProvider sp)
CallSiteRuntimeResolver.VisitFactory(FactoryCallSite factoryCallSite, RuntimeResolverContext context)
CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)
CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
<73 more frames...>
TestExecutionEngine.FireEventsAsync(HookType hookType)
TestExecutionEngine.FireEventsAsync(HookType hookType)
TestExecutionEngine.FireScenarioEventsAsync(HookType bindingEvent)
TestExecutionEngine.OnScenarioEndAsync()
TestRunner.OnScenarioEndAsync()
UserGroupSettingsFeature.TestTearDownAsync()
GenericAdapter`1.GetResult()
AsyncToSyncAdapter.Await(Func`1 invoke)
SetUpTearDownItem.RunSetUpOrTearDownMethod(TestExecutionContext context, IMethodInfo method)
SetUpTearDownItem.RunTearDown(TestExecutionContext context)

This is the code:

 [Binding]
 public class SetUpTearDown
 {
     private readonly IEmailService _emailService;
     private readonly ScenarioContext _scenarioContext;
     private readonly DatabaseSteps _databaseSteps;
     private readonly Randomizer _randomizer;
     private readonly WebClientSteps _webClientsSteps;
     private readonly ISessionData _sessionData;
     private readonly IMessagingClient _messagingClient;
     private readonly AzureSteps _azureSteps;
     private readonly OrchestrationSteps _orchestrationSteps;
     private readonly BaseSteps _baseSteps;
     private SalesForceSteps _salesForceSteps { get; }
     public static IConfigurationRoot Configuration { get; set; }

     public SetUpTearDown(
         DatabaseSteps databaseSteps,
         IEmailService emailService,
         Randomizer randomizer,
         ScenarioContext scenarioContext,
         WebClientSteps webClientsSteps,
         ISessionData sessionData,
         IMessagingClient messagingClient,
         AzureSteps azureSteps,
         OrchestrationSteps orchestrationSteps,
         BaseSteps baseSteps,
         SalesForceSteps salesForceSteps)
     {
         _databaseSteps = databaseSteps;
         _emailService = emailService;
         _randomizer = randomizer;
         _scenarioContext = scenarioContext;
         _webClientsSteps = webClientsSteps;
         _sessionData = sessionData;
         _messagingClient = messagingClient;
         _azureSteps = azureSteps;
         _orchestrationSteps = orchestrationSteps;
         _baseSteps = baseSteps;
         _salesForceSteps = salesForceSteps;
     }

     [ScenarioDependencies]
     public static IServiceCollection CreateServices()
     {
         var assemblyConfigurationAttribute = typeof(SetUpTearDown).Assembly
             .GetCustomAttribute<AssemblyConfigurationAttribute>();
         var buildConfigurationName = assemblyConfigurationAttribute?.Configuration;

         if (string.IsNullOrEmpty(buildConfigurationName))
         {
             throw new Exception("Cannot retrieve build configuration name to load configuration settings!");
         }

         Configuration = new ConfigurationBuilder()
             .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
             .AddJsonFile($"appsettings.{buildConfigurationName}.json", optional: true, reloadOnChange: true)
             .AddEnvironmentVariables()
             .Build();

         // create container with the runtime dependencies
         var services = new ServiceCollection();

         // Logging
         services.AddLogging();
.................................................................
   #region Before Scenarios
   [BeforeScenario("defineDeletionMarker", Order = 0)]
   public void DefineDeletionMarker()
   {
       _scenarioContext.SetInContext(ScenarioContextKeys.DeletionMarker, $"{GlobalConstants.DeletionMarker}{_randomizer.GetString(4)}_");
   }
.................................................

[clrudolphi]

The stack trace implies the problem is occurring during an AfterScenario hook. Can you share that code?

I'm a bit confused by the snippets of code shared so far. Is the ScenarioContext parameter in the constructor of the SetupTearDown class a Reqnroll.ScenarioContext or some other class within your solution that happens to have the same name? I ask b/c there is no .SetInContext() method available on the Reqnroll.ScenarioContext class (as shown being used in the BeforeScenario hook method).

Without further info, my general suggestion would be to inject the Reqnroll.ScenarioContext as a method argument into the hook methods that need it (rather than as a constructor parameter).

[304NotModified]

Please also list the used packages & versions and include the namespace in the callstack.

While Migrating, sometimes there is also a (indirect) reference to SpecFlow, which won't mix well with Reqnroll

[iarsova]

Hey. Thanks for dealing with this and I am truly sorry if I am making your days harder :)

1. "The stack trace implies the problem is occurring during an AfterScenario hook. Can you share that code?" - There is no stack trace. The code never reaches the Before or After scenario.
2. "Is the ScenarioContext parameter in the constructor of the SetupTearDown class a Reqnroll.ScenarioContext" - YES;
3. "Without further info, my general suggestion would be to inject the Reqnroll.ScenarioContext as a method argument into the hook methods that need it (rather than as a constructor parameter)." - I tried this as well and the result is the same, the error is the same;
4. The list is:

[clrudolphi]

A few observations on this list of package references:

• If the migration from SpecFlow is complete, then you may remove the dependency on Reqnoll.SpecFlowCompatibility. If not, please let us know which capabilities of the SpecFlow namespaces are yet still in use.
• This list includes dependencies on both MsTest and NUnit. I doubt this is causing your problems but can't rule it out.

[iarsova]

SetupTearDown.txt

[iarsova]

I have one more question. Why with SpecFlow we were able to use ScenarioContextx as a constructor parameter, but with Reqnroll we need to inject the Reqnroll.ScenarioContext as a method argument into the hook methods?
We have so much Before and AfterScenario methods and it will be a lot of work to refactor the SetupTeardown

[clrudolphi]

I have been trying to recreate with no luck.
You earlier had included this text:

This is the only stack trace I have:

Message: 
Reqnroll.ReqnrollException : Unable to access test execution dependent service 'Reqnroll.ScenarioContext' with the Reqnroll.Microsoft.Extensions.DependencyInjection plugin. This service is only available once test execution has been started and cannot be used in '[BeforeTestRun]' hook. See https://go.reqnroll.net/doc-migrate-specflow-testrun-hooks for details.
TearDown : Reqnroll.ReqnrollException : Unable to access test execution dependent service 'Reqnroll.ScenarioContext' with the Reqnroll.Microsoft.Extensions.DependencyInjection plugin. This service is only available once test execution has been started and cannot be used in '[BeforeTestRun]' hook. See https://go.reqnroll.net/doc-migrate-specflow-testrun-hooks for details.

This message mentions "TearDown" (at the beginning of the 2nd line of the 'Message'). Is that a class or method you've not yet shared with us? If so, please share if you can.

[clrudolphi]

nm, figured that out. The text TearDown is displayed by NUnit when an exception is thrown during its tear down stage. So the same exception message is being printed twice.