When running a SpecFlow test using nunit-console v13.15.4 with steps that are defined in another assembly, it says that "no matching step was found". The specflow.json file is present in the test assemblies output directory. It is defined as below:
Full command line being used:
nunit3-console "Tests\App\Org.App.Specs\bin\Configuration\net6.0-windows10.0.19041.0\Org.App.Specs.dll" --where test=~AutotestName --noheader --trace Debug
Adding --work "Tests\App\Org.App.Specs\bin\Configuration\net6.0-windows10.0.19041.0 where the specflow.json is located didn't help.
Running the same test using the dotnet test command does not produce this issue. The step assembly is found and the test is executed as expected.
Versions of NUnit/NUnit Console:
NUnit: 3.13.3
Nunit3TestAdapter: 4.4.2
NUnit-Console: 13.15.4 (.zip downloaded from the project releases on GitHub; the inprocess option was not available on my platform)
When running a SpecFlow test using nunit-console v13.15.4 with steps that are defined in another assembly, it says that "no matching step was found". The specflow.json file is present in the test assemblies output directory. It is defined as below:
Full command line being used:
nunit3-console "Tests\App\Org.App.Specs\bin\Configuration\net6.0-windows10.0.19041.0\Org.App.Specs.dll" --where test=~AutotestName --noheader --trace Debug
Adding--work "Tests\App\Org.App.Specs\bin\Configuration\net6.0-windows10.0.19041.0
where the specflow.json is located didn't help.Running the same test using the
dotnet test
command does not produce this issue. The step assembly is found and the test is executed as expected.Versions of NUnit/NUnit Console: NUnit: 3.13.3 Nunit3TestAdapter: 4.4.2 NUnit-Console: 13.15.4 (.zip downloaded from the project releases on GitHub; the inprocess option was not available on my platform)
The logs are attached to the issue: InternalTrace.33708.Org.App.Specs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null.log InternalTrace.33708.log