SpecFlow Visual Studio Integration 2017.1.10 Released

A new update to the Visual Studio Integration for SpecFlow has been released for Visual Studio 2013, 2015 and 2017. This release contains the following changes:

  • Fix to run feature files in projects using the new project model introduces in VS 2017. More details here
  • Scenario outlines can now be executed from Visual Studio with SpecFlow+ Runner
  • Additional logging
  • Fix for running tests by right-clicking with Resharper

Thank you to all the contributors!

SpecFlow+ Runner 1.6.3 Released

SpecFlow+ Runner 1.6.3 has been released and is available to download from nuget.org.

This minor release fixes two bugs:

  • CommunicationObjectFaultedException thrown when using process separation in conjunction with DateTime
  • CommunicationObjectFaultedException with tests that take a long time to complete. This was caused by a time limit of 10 minutes for responses; the time limit has been extended to 24 hours.

SpecFlow+ Runner 1.6.2 Minor Release

SpecFlow+ Runner 1.6.2 is now available to download from NuGet.org. This release addresses two issues in SpecFlow+ Runner:

  • Workaround for issue 935, where the project name and projectId (GUID) are not automatically entered in your profile when installing the package.
    Note: You will still need to manually enter a GUID in your profile if you are using SpecFlow+ Server for adaptive testing. The projectId should be the GUID of the project (this is the <ProjectGuid> in your .csproj, although in theory you can enter any valid GUID here).
  • Thread.Current.Name again returns “Test Thread #<Number>” when executing tests in multiple threads

SpecFlow+ LivingDoc 0.1.9 Released

SpecFlow+ LivingDoc has been updated. If you are using the VSTS version, you will automatically receive this update. TFS users will need to download the extension from the marketplace.

This release introduces a number of UX improvements and additional features:

  • Click on Show source when viewing the documentation to switch to the source file in TFS/VSTS or on GitHub, where you can also edit the file.
  • You no longer need to specify a .csproj file to build the documentation. Instead, you can point to a folder. The documentation includes all features files in your folder and its child tree. This allows you to build a living documentation from feature files used by projects that are not developed in C#.
  • The version number is now displayed along with your license information when mousing over the licensee.

SpecFlow+ Runner 1.6.1 Released

SpecFlow+ Runner 1.6.1 is now available from NuGet. This minor release and adds support for the “Run Functional Tests” task in TFS/VSTS and fixes the following issues:

  • Project paths containing a hash character (‘#’) no longer cause a file not found exception
  • Tests are no longer duplicated in the Test Explorer in VS

Issue with SpecFlow+ Runner and Latest Visual Studio 2017 Version

Update: SpecFlow+ Runner 1.6.2 includes a fix for this issue. You now only need to enter a GUID if you are using the SpecFlow+ server (for adaptive test scheduling), as the GUID is used as the unique key for the test results.


We have discovered an issue that affects SpecFlow+ Runner with Visual Studio 2017. When adding the NuGet package to your project, a default profile is added to your project (default.srprofile). During the installation process, the projectName and projectId should be entered automatically in this profile.

When installing the packages with the latest version of Visual Studio 2017, the projectName and projectId are no longer filled in automatically. This results in your tests not being discovered, meaning they cannot be executed.

As a workaround, you can enter the projectName and projectId in your profile yourself. The projectName should be the name of the project you added the NuGet package to; the projectId should be the GUID of the project (this is the <ProjectGuid> in your .csproj, although in theory you can enter any valid GUID here).

An issue has already been opened, and you can track the status here.

SpecFlow+ 1.6 Released

SpecFlow+ 1.6.0 has been officially released and can now be downloaded.

SpecFlow+ Runner

New Features

  • Support for SpecFlow 2.2.0
  • Execution time of scenarios and features added to standard report template
  • New configuration setting to handle conflicts with existing report files with the same name (overwrite, rename)
  • Support for placeholders in additional report file names (current date and time, project GUID)
  • Report template for JSON output
  • Report template for XML output
  • Added option for CopyFolder DeploymentStep to disable cleanup of target folder before copying


Bug Fixes:

  • Filters for functional tests now use same syntax as everywhere else
  • Execution via Visual Studio TestAdapter (VS or TFS) now takes into account entries in TestAssemblyPaths and no longer executes all given assemblies
  • testpath filter now works with colon (:) in scenario title
  • Use projectName in SpecFlow+ server if no project name is specified in the .srprofile file

SpecFlow+ Excel

New Features:

  • Scenario description now supported
  • Support for SpecFlow 2.1 & 2.2


Bug Fixes:

  • Better recognition of Gherkin keywords in rows

SpecFlow 2.2.0 Released

SpecFlow 2.2.0 has been officially released and can now be downloaded.

Core Changes:

  • Projects are now read by XML instead of using MSBuild. The general functionality is working. If something is missing or you experience any problems, please submit an issue and look here
  • Before/AfterFeature Hooks can now access the FeatureContext by parameter, see #779
  • Upgrade to BoDi 1.3, see #876

New Features:

  • MsTest: Support for [DeploymentItem] attribute with @mstest:DeploymentItem tag (Issue 803)
  • JSON configuration support: You can also store your SpecFlow configuration in specflow.json (#690)
    Examples can be found here.
    Note: This change required some small changes to the plugin interface; some custom plugins may therefore no longer work correctly.
  • Order sensitive overload for compare to set #778
  • TestThreadContext can be used for test thread related data sharing (#875)
  • Support for xUnit2 ITestOutputHelper (#874)


  • Removed obsolete StepScopeAttribute – use the ScopeAttribute instead
  • Fixed: Projection.Equals() returns false unnecessarily if table headers differ from property name by casing
  • Fixed regex-less step definition support, see StepDefinitionsWithoutRegex.feature for details (Issues #715#301)
  • Fix in executing the code behind generation #855
  • Fixed hooks with multiple tags executing more than once #848
  • Fix code behind generation if it is triggered by a Save command in Visual Studio (#877)

SpecFlow VS Integration 2017.1 Released

SpecFlow Visual Studio integration 2017.1 has been released. This version introduces basic support for Visual Studio 2017, as well as supporting earlier versions of Visual Studio. There are however some limitations when using Visual Studio 2017:

  • This version does not support the new project system in Visual Studio 2017. Support for the new project system will be introduced in a future release.
  • This version does not provide support for .NET Core.


In addition to Visual Studio 2017 support, this release includes the following changes:


If you notice any issues, please report them here.

SpecFlow+ Runner 1.5 Released

SpecFlow+ Runner 1.5 has been released. This minor release introduces the ability to output multiple reports (defined in the <Report> element of your profile) in a single test run and fixes some small formatting issues with whitespace in reports.