https://www.departmentofproduct.com/blog/writing-bdd-test-scenarios/

A BDD scenario is a written description of your product’s behavior from one or more users’ perspectives. Scenarios are designed to reduce the cost of translation and make it easier for your engineers to understand the requirements and for your QA (if you have one) to test it properly.

In its simplest format, there are 3 key elements in any BDD scenario:

GIVEN(describing the context)

WHEN (describing the action)

THEN (describing the outcome)

Example:

Scenario 1: User successfully creates a LinkedIn Account

Context - GIVEN John is on the LinkedIn Registration page

Action - WHEN he enters all required registration fields

Outcome - THEN a LinkedIn account is created

next level👇

When you require more information in a scenario, an ‘AND’ can be used after any of the descriptors:

GIVEN(context),

AND(further context),

WHEN(action/event),

AND(further action/event),

THEN(outcome)

AND(further outcome)

Example:

GIVEN John is on LinkedIn Registration page

WHEN he enters all the required registration information

AND he hits ‘join now’

THEN his LinkedIn account is created