Tuesday, February 9, 2016

SpecFlow v2 finally arrived

We had to wait for it a long time, but now it’s finally there, a new release of SpecFlow; my favorite  Behaviour-Driven Development (BDD) tool.

So what’s new?

Important changes in SpecFlow V2 include:

  • All components upgraded to .NET 4.5.
  • Upgraded to the new Gherkin 3 parser
  • 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 and CompareToInstance.
  • 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

If you never used SpecFlow before, now is a good time to try it out. Writing tests will never be the same again…

Remark: If you are already using SpecFlow today, don’t forget to check the upgrade guide: http://www.specflow.org/updating-to-specflow-2/

No comments: