Troubleshooting Visual Studio Integration
If Visual Studio displays the error message
Cannot find custom tool 'SpecFlowSingleFileGenerator' on this system. when right-clicking on a feature file and selecting
Run Custom Tool, make sure the SpecFlow extension is enabled.
To enable the extension in Visual Studio, select Tools | Extensions and Updates..., select the "SpecFlow for Visual Studio" extension, then select Enable.
You can enable traces for SpecFlow. Once tracing is enabled, a new
SpecFlow pane is added to the output window showing diagnostic messages.
To enable tracing, select Tools | Options | SpecFlow from the menu in Visual Studio and set Enable Tracing to 'True'.
Steps are not recognised even though there are matching step definitions
The SpecFlow Visual Studio integration caches the binding status of step definitions. If the cache is corrupted, steps may be unrecognised and the highlighting of your steps may be wrong (e.g. bound steps showing as being unbound). To delete the cache:
- Close all Visual Studio instances.
- Navigate to your
%TEMP%folder and delete any files that are prefixed with
- Reopen your solution.
You may receive a more specific error message if you enable tracing (see above).
Tests are not displayed in the Test Explorer window when using SpecFlow+ Runner
Note: As of Visual Studio 2017 15.7 the temporary files are no longer used. The following only applies to earlier versions of Visual Studio.
The Visual Studio Test Adapter cache may also get corrupted, causing tests to not be displayed. If this happens, try clearing your cache as follows:
- Close all Visual Studio instances
- Navigate to your
%TEMP%\VisualStudioTestExplorerExtensions\folder and delete any sub-folders related to SpecFlow/SpecRun, i.e. that have "SpecFlow" or "SpecRun" in their name.
- Reopen your solution and ensure that it builds.
Unable to find plugin in the plugin search path: SpecRun` when saving / generating feature files
SpecFlow searches for plugins in the NuGet packages folder. This is detected relative to the reference to
TechTalk.SpecFlow.dll. If this DLL is not loaded from the NuGet folder, the plugins will not be found.
A common problem is that the NuGet folder is not yet ready (e.g. not restored) when opening the solution, but
TechTalk.SpecFlow.dll in located in the
bin\Debug folder of the project. In this case, Visual Studio may load the assembly from the
bin\Debug folder instead of waiting for the NuGet folder to be properly restored. Once this has happened, Visual Studio remembers that it loaded the assembly from
bin\Debug, so reopening the solution may not solve this issue. The best way to fix this issue is as follows:
- Make sure the NuGet folders are properly restored.
- Close Visual Studio.
- Delete the
bin\Debugfolder from your project(s).
- Reopen your solution in Visual Studio.
Tests are not displayed in the Test Explorer window when using SpecFlow+ Runner, even after after restoring the NuGet package
SpecRun.Runner NuGet package that contains the Visual Studio Test Explorer adapter is a solution-level package (registered in the
.nuget\packages.config file of the solution). In some situations, NuGet package restore on build does not restore solution-level packages.
To fix this, open the NuGet console or the NuGet references dialog and click on the restore packages button. You may need to restart Visual Studio after restoring the packages.
VS2015: Tests are not displayed in the Test Explorer window when using SpecFlow+ Runner
It seems that VS2015 handles solution-level NuGet packages differently (those registered in the
.nuget\packages.config file of the solution). As a result, solution-level NuGet packages must be listed in the projects that use them, otherwise Test Explorer cannot recognise the test runner.
To fix this issue, either re-install the SpecFlow+ Runner NuGet packages, or add the dependency on the
SpecRun.Runner package (
<package id="SpecRun.Runner" version="1.2.0" />) to the packages.config file of your SpecFlow projects. You might need to restart Visual Studio to see your tests.