This Gherkin Language uses a set of special keywords to give the structure to a Scenario with a proper meaning to it. Each keyword is translated to many spoken languages; in this reference, we’ll use English.

Most lines in a Gherkin document start with one of the keywords.

Comments are only permitted at the start of a new line, anywhere in the feature file. They begin with zero or more spaces, followed by a hash sign (#) and some text.

Block comments are currently not supported by Gherkin.

Gherkin Language supports many different frameworks to write the scenarios mainly the Behavior Driven Development framework.

With the use of this language, the Scenario becomes more readable and more meaningful.

The development is now starts with defining the behavior of the application and the behavior is written in the form of Features and under Features, there will be different scenarios that define different behavior of the application

The main reason behind using this language is that the developer, tester, customer representatives, all should commonly define the behavior of the application using Gherkin language. This will help all the stakeholders and panel members to be on the same page and using this behavior all the scenarios will get created and the product will be developed.