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)

Fixes:

  • 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.

SpecFlow V2.1 Released

SpecFlow V2.1 has been officially released and is available to download from NuGet. The most important changes are:

  • Updated to Gherkin 4.0.0 parser
  • Plugin interface for generator and runtime plugins
  • Changed to an event-based interface and added additional hooks for customizing TestThread and scenario dependencies
  • Two new assist methods, FindInSet and FindAllInSet.

The following issue has been fixed:

  • Issue #246: steps without regular expressions cannot pass negative numbers as arguments

You can read full changelog here.

SpecFlow+ V1.4 Released

25 May 2016

SpecFlow+ V1.4 has been officially released and is available to download from NuGet. The most important changes are:

  • Updated SpecFlow+ Excel for SpecFlow 2 compatibility (compatible with SpecFlow 2.1)
  • Support for SpecFlow V2’s shared AppDomain parallelisation
  • Use the “about” option to display additional license info (expiry date, upgrade until date) from the command line
  • Report API documentation

Bug fixes:

  • Failed tests are not retried under certain circumstances
  • Not all tags are displayed as traits in Visual Studio 2015 Update 2

SpecFlow 2 Pre-release with Updated Gherkin Parser

A new SpecFlow 2 pre-release package (SpecFlow 2.1.0-preview20160412-16) is available on NuGet:

  • Updated Gherkin parser
  • Improved output support for the specflow.exe GenerateAll command
  • Improved debugging support for the specflow.exe GenerateAll command

Note: This is a pre-release version; the package will only show up in the NuGet package manager in Visual Studio if you chose to “Include prereleases”.

SpecFlow+ Excel 1.4 Release Candidate

SpecFlow+ Excel has been updated for compatibility with SpecFlow 2. A pre-release version is now available on NuGet. This package requires an updated pre-release version of SpecFlow 2 that will automatically be installed with the SpecFlow+ Excel package. The new SpecFlow 2 package includes an updated Gherkin parser required by the Excel plugin. SpecFlow+ Runner has also been updated to this new version.

Note: This is a pre-release version; the package will only show up in the NuGet package manager in Visual Studio if you chose to “Include prereleases”.

SpecFlow+ Runner 1.4 Release Candidate

SpecFlow+ Runner 1.4 has been released on NuGet.org. This is a pre-release version, so the package will only show up in Visual Studio if you have chosen to display pre-releases.

This release introduces SharedAppDomain support for test thread isolation in order to use the parallelization features introduced with SpecFlow 2.

You can also read more about parallelisation in SpecFlow+ on developer Andreas Willich’s blog.

SpecFlow V2 Release

Before installing the new version, please read the information on updating. The installation procedure is also covered there. Note that SpecFlow 2 requires .NET 4.5 or higher!

WHAT’S NEW IN SPECFLOW V2?

Important changes in SpecFlow V2 include:

  • All components upgraded to .NET 4.5.
    Note: SpecFlow v2 will no longer work with older .NET runtimes!
  • Upgraded to the new Gherkin 3 parser
    Note: This change may mean that older feature files are no longer parsed correctly!
  • Support for parallel SpecFlow tests within the same AppDomain
  • Visual Studio integration has been separated to a separate project
  • Support for xUnit 2.0 and NUnit 3.0, including parallel test execution. The older providers have been retained and renamed (to xunit.1 and nunit.2 respectively).
  • Ability to determine the execution order of hooks (e.g. [BeforeScenario])
  • Extensible table conversions and comparisons for CreateSet, CreateInstance, CompareToSet andCompareToInstance.
  • Access the details of the currently executed step with ScenarioContext.StepContext
  • Display tags in NUnit test adapter in Visual Studio
  • Better regular expression suggestions generated for missing steps with quoted parameters
  • Steps base class provides properties for thread-safe access to feature, scenario and step contexts
  • Scenario and feature context can be injected to the binding class, avoiding static ScenarioContext.Current and FeatureContext.Current accessors
  • Better matching of column names to property names by removing characters that are invalid in property names
  • Small improvements in the DI framework
  • Easily configure SpecFlow to work with MSTest using the SpecFlow.MsTest NuGet package
  • Test execution report now includes “tags” in the NUnit report, which can be displayed using a custom XSLT
  • Removed .NET runtime version from generated file headers to avoid unwanted changes

You can find the full changelog here. More information on parallel execution is available in the documentation here.