In the last years, I've met several project teams doing SpecFlow testing. For almost all of them the biggest challenge was to improve the efficiency of the automated testing process. Typical questions are about organizing feature files, keeping the specification language consistent, refactoring feature files, automation code maintainability, better feedback from failing tests, test execution time or handling stability issues. Some people were asking me if BDD/SpecFlow scales well for projects beyond BookShop? (It does.)
Every project is different, so their problems are. Still, I have collected a handful ideas that make sense to consider. In this session I would like to show you some of these, through examples from real projects wherever it is possible. You will see in detail the application of the page object pattern, the organization of Ghekin files to a feature tree and also the different ways of applying the default value pattern. These ideas are shown in scope of .NET and SpecFlow, but also applicable to automated testing solutions in other fields.