Issue with ScenarioDependencies.Scope — Not Invoked Per Scenario

[TimMurphy]

Description:

I have successfully installed and configured the Reqnroll.Microsoft.Extensions.DependencyInjection package. My service collection method, GetServices(), is decorated with the attribute:

[ScenarioDependencies(ScopeLevel = ScopeLevelType.Scenario)]

The Issue:

While debugging, I found that GetServices() is only called once — during the initial setup. I expected that it would be invoked at the start of every new scenario. This behavior seems to contradict Rule 1 https://docs.reqnroll.net/latest/automation/context-injection.html

The life-time of these objects is limited to a scenario’s execution.

Questions:

1. Is it expected behavior for GetServices() to be called only once under this configuration?
2. If not, what might be causing this behavior, and how can I ensure it is invoked before each scenario execution?

Any insights or suggestions to help resolve this inconsistency would be greatly appreciated.

[hotchkj]

Complete agree, for what it's worth. The total opposite of what I was expecting, and not what the original SpecFlow equivalents did either. So far I don't see how Reqnroll.Microsoft.Extensions.DependencyInjection is intended to be workable - services with singletons should not be shared across entirely independent tests.

[gasparnagy]

@TimMurphy @hotchkj Could you please have a look / try if the new design prototype would be better fitting? https://github.com/orgs/reqnroll/discussions/472