SpecFlow hooks (or events) are extension points where you can insert custom automation logic into the scenario execution before or after different sections, for example before any scenario execution. These can be used to perform custom preparation or cleanup logic, e.g. resetting the database. In bigger projects, you might need to have multiple hooks of […]
The format of the feature files used in Cucumber or SpecFlow is very simple. The format (or grammar), called Gherkin, was intentionally designed to be simple, so that the specification written in these files are kept simple and understandable. There are no loops or ifs. The only special structure you can make in a feature […]
As announced in December, we have published the pre-release version of SpecFlow v2. As hopefully the final version is also going to be released soon, it is good to be prepared how you can upgrade your existing projects to the new version.
On the bases of feedback and issues, a lot of SpecFlow users seem to try to put step definitions and other binding codes to base classes. I’ll try to explain why inheritance doesn’t fit to the concept of global step definitions used by SpecFlow.