Open nieldy opened 6 months ago
I can confirm this issue is still happening. I switched everything from Specflow to Reqnroll and my step definitions are not being recognized from an external assembly (also using reqnroll).
this is my reqnroll.json file
{
"$schema": "https://schemas.reqnroll.net/reqnroll-config-latest.json",
"bindingAssemblies": [
{
"assembly": "StepDefinitions.Base"
}
]
}
I have the same problem here.
I tried it with the template reqnroll project with net6.0, net7.0 and net8.0 but all with the same result. Actually net6.0 does work fine but not with cucumber expression, but the others still have the same error Cannot find a matching step definition
dotnet new reqnroll-project -f net6.0
I have a lot of common steps in an external NuGet package. The assembly is referenced under
stepAssemblies
in thespecflow.json
file. I.e.I'm finding that the external steps aren't being recognised in the feature files. I get the warning
Cannot find a matching step definition
and no auto-completion hints when typing a step. The step however does run correctly when the test is executed. Note that steps defined within the test project itself are being recognised correctly.I have tried restarting Rider, unloading and re-loading the project and disabling and re-enabling the plugin.
Note that the package is still using SpecFlow (not Reqnroll). The test project that's referencing the assembly is also using SpecFlow.
I'm running tests using
SpecFlow.MsTest
.