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: Baseclass or Context Injection
by Gáspár on February 3, 2017
We need to access different services and data from multiple step definition classes. Shall we use base classes or context injection for that? — This question has popped up at two of my clients, so I thought it would be worth discussing it also in a blog post.
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.