In this section, we will delve into the core structure of Gherkin scenarios: the Given, When, Then format. This format is essential for writing clear and understandable behavior-driven development (BDD) tests. By the end of this section, you will be able to write effective scenarios using these keywords.

1. Given: Sets up the initial context of the scenario. It describes the state of the system before the main action occurs.
2. When: Describes the action or event that triggers the behavior you want to test.
3. Then: Specifies the expected outcome or result after the action is performed.

• Purpose: To establish the initial conditions or context.
• Example: "Given a user is logged into the application."

• Purpose: To describe the action that the user or system performs.
• Example: "When the user clicks on the 'Submit' button."

• Purpose: To define the expected outcome or result of the action.
• Example: "Then the user should see a confirmation message."

Let's look at a complete scenario using the Given, When, Then format:

• Given the user is on the login page: Sets the initial state where the user is ready to log in.
• When the user enters valid credentials: Describes the action of entering correct login details.
• And the user clicks the login button: Continues the action sequence with another step.
• Then the user should be redirected to the dashboard: Specifies the expected result of a successful login.
• And the user should see a welcome message: Adds another expected outcome to verify.

Task: Write a Gherkin scenario for a user searching for a product on an e-commerce website.

• Common Mistake: Avoid using technical jargon in scenarios. Keep the language simple and business-oriented.
• Tip: Use "And" to continue actions or outcomes that are part of the same step type (Given, When, or Then).

The Given, When, Then format is a powerful tool for writing clear and concise BDD scenarios. By structuring your tests in this way, you ensure that they are easy to read and understand, which is crucial for effective communication among team members. In the next section, we will explore how to create step definitions that bring these scenarios to life in your code.