Specflow is a tool that allows writing tests using a business-readable domain-specific language called Gherkin. It supports features, scenarios, and steps to describe system behaviors in a natural language format. Specflow code generates glue code that maps Gherkin steps to automated test methods.

1. Using Specflow for BDD

3. Specflow Installation
Demo

4. Gherkin Language

6. Features
Contain One or more scenarios
Group/Contain logically related scenarios
Represent small, discrete features of the system

7. Features
Start with “Feature:” keyword
Followed by feature name/terse description
Optional free text description
Feature: Brush Teeth
Brushing teeth is good
because it helps keep
them clean

8. Feature
As a ….. I want ….. So that …..
In order to … as a ….. I want

9. Scenarios
Concrete examples of expected system behaviour
Each scenario describes a particular situation
Each scenario should be independent and isolated from other scenarios
Can represent
- Happy Paths
- Error Paths
- Edge Cases
Start with “Scenario:” keyword
Followed by title
Scenario: Successful Brushing

10. Scenario Steps

11. Tags
Mark features and scenarios with arbitrary tags
Map to unit test framework “categories”
Scenarios inherit feature tags
Can have multiple tags
Tags specified using @
@ignore is a special case

12. Using Data Tables in Steps
Allow tabular data to be passed to individual step
Useful for specifying large data rather than multiple steps

13. Scenario outlines

14. Background
Provides context (state setup) to the scenarios in a feature
Executed before any scenario

15. Coding the Automated
Steps
Demos

16. Coding the automated steps

17. Linking TFS with
SpecFlow