Gherkin makes test scenarios easy to read

A human-readable description follows the feature.

You can write anything you like, as long it doesn’t start with a Gherkin-keyword.

A single Gherkin scenario is a flow of events through the Feature being described and maps 1:1 with an executable test case for the system.

You can have multiple Scenarios in one Feature-file.

A human-readable description follows the scenario.

You can write anything you like, as long it doesn’t start with a Gherkin-keyword.

Given steps are used to describe the initial context of the system – the scene of the scenario. It is typically something that happened in the past.

And-keyword is used to extend to your steps.

Helps you to elaborate your feature-file further.

When keyword defines the test action which will be executed.

By test action we mean the user input action.

Then keyword defines the outcome of previous steps.

You can place tags above Feature to group related features, independent of your file and directory structure.

Furthermore you can filter tags within your CI/CD-pipeline.

Delimited parameters <> are used as references which are referred to in the example tables. SpecFlow will automatically replace these parameters when executing tests.

Data Tables are handy for passing a list of values to a step definition. A useful tool in complex Gherkin examples.