A way of designing software that focuses on how people actually use the product rather than just how the code is written.

What is BDD

A meeting where the person who wants the feature, the person building it, and the person testing it talk to agree on how it should work.

The Three Amigos

Using everyday words that everyone on the team understands instead of using confusing technical terms.

A short, simple sentence that describes who the user is, what they want to do, and why they want to do it.

Using specific, concrete stories to explain exactly how the software should act in a real situation.

A special way to write down examples using simple words like Given, When, and Then so that both people and computers can read them.

Using the word 'Given' to describe the starting situation or what has already happened before a user takes action.

Using the word 'When' to describe the specific thing a user does, such as clicking a button or entering a password.

Using the word 'Then' to describe the outcome or what the user should see after they take an action.

Using the word 'And' to include extra steps or conditions in a story without making it hard to read.

Using a simple table to check if the software works correctly with many different sets of information at once.

A basic text document that holds all the examples and rules for one specific part of the software.

Using a computer program to instantly verify that the software is following all the agreed-upon rules.

A session where the team brainstorms a new idea to find hidden details and solve potential problems before they start building.

The process of turning rough notes and ideas from a meeting into clear, structured examples that are ready to be used.

Designing software by starting with what the user needs to achieve and working backward to the technical parts.