Gáspár Nagy on software

coach, trainer and bdd addict, creator of SpecFlow

SpecFlow without code-behind files and a big step towards .NET Core support

by Gáspár on April 24, 2017

SpecFlow uses generated code-behind files for executing the scenarios. Not because we like code-behind files, but because this was the only way we could easily integrate Cucumber-style Behavior Driven Development to the .NET developer toolset. But after almost 8 years, can we get rid of the code-behind files finally? And how is it related to […]

SpecFlow tips: Customizing dependency injection with Autofac

by Gáspár on August 18, 2016

SpecFlow creates and disposes the instances of your step definition classes automatically. It also allows injecting dependencies to these classes through a feature called context injection. This article shows how this injection can be configured to use the popular Autofac dependency injection framework.

SpecFlow Tips: Collect more information on error (part 2)

by Gáspár on May 13, 2016

In the first part of this article I described why it is important to provide more information on errors and how you can collect useful artifacts (screenshots, log files, etc.) in an [AfterScenario] hook. In this part I would like to explain how to write more informative assertions.

SpecFlow Tips: Run only specific scenarios in TFS/VSTS build

by Gáspár on May 11, 2016

Many teams who use SpecFlow setup their continuous integration environment with Microsoft Team Foundation Server (TFS) or its cloud based service, the Visual Studio Team Services (VSTS, fka VSO). TFS/VSTS has an improved build system, where it is much easier to setup and customize builds. Regardless of the fact, which unit test provider you use […]