Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

Behaviour-driven development (BDD): definition, scenarios and related notions

Domain

Engineering

In brief

Behaviour-driven development (BDD) is a software development approach in which the business, developers and testers describe the expected behaviour of an application through concrete examples, written as scenarios in the vocabulary of the business. These scenarios serve as acceptance criteria and can run as automated tests.

Page contents

Definition of behaviour-driven development

“Development driven by behaviour”: the literal reading of behaviour-driven development (BDD) conveys the idea. The approach describes what an application must do through examples of behaviour, expressed in the vocabulary of the business before the code is written. Dan North, who coined the term, uses the British spelling, “behaviour-driven development”.

His article “Introducing BDD” (dannorth.net, read on 12 November 2026) mentions a first publication in Better Software magazine in March 2006. Dan North presents BDD there as his answer to the questions developers asked him when he taught test-driven development (TDD): where to start, what to test, how to name a test. He replaces the word “test” with the word “behaviour”. With the analyst Chris Matts, he then extends this vocabulary to the expression of requirements: the expected behaviour of a user story, he writes, is its acceptance criteria.

Discover, formulate, automate

The documentation of the Cucumber tool (cucumber.io, read the same day) describes BDD as a way of working that brings business people and technical people closer together. It expects from it a shared understanding of the problem to be solved and documentation that is automatically checked against the behaviour of the system. It distinguishes three practices, whose names we keep.

  1. Discovery: around an upcoming change, the team discusses concrete examples to agree on what is expected.
  2. Formulation: these examples are recorded in a form readable by a person and by a machine.
  3. Automation: each example is connected to the system in the form of a test, which guides the writing of the code.

The Given, When, Then scenario

Dan North’s article gives the scenario its form: Given, an initial context; When, an event; Then, expected outcomes. The Gherkin language, which Cucumber reads, takes up these keywords. Its documentation gives them French equivalents, among them “Étant donné que”, “Quand” and “Alors”.

Take a rule from a rail booking website: an exchangeable ticket can be exchanged up to the day before departure.

  • Given a traveller holds an exchangeable ticket
  • When they request an exchange the day before departure
  • Then a new ticket is issued
  • And the old ticket is cancelled

Each line is connected to a piece of code that prepares the context, triggers the event or checks the outcome. Other tools follow this principle, such as JBehave, whose writing Dan North dates to the end of 2003.

BDD, TDD, acceptance tests: not to be confused

TDD, whose cycle is recalled in our article on automated testing, is a developer discipline. BDD grew out of it and then, according to Dan North, broadened to analysis and automated acceptance testing.

In common usage, an acceptance test checks that a delivered function meets its criteria. It can exist without BDD, for example in the form of manual acceptance testing. BDD concerns the way these criteria are obtained: examples discussed by several people, written before the code.

A Gherkin scenario is not by nature an end-to-end test. The Cucumber documentation advises writing examples without assumptions about the technology or the interface: implementation details stay in the code connected to the steps.

The conditions of the approach and its limits

BDD relies on the business taking part in the discussion of examples, at the point where a user story receives its acceptance criteria; our article on agile story mapping places this step. Scenarios written by the technical team alone keep the form of the approach and lose its purpose, which is agreement on the requirement.

Automated scenarios are code to maintain, along with the steps that connect them to the application. A calculation rule with many cases can be checked by unit tests, which are faster, rather than by as many scenarios.

How checks are divided between scenarios, unit tests and integration tests is a matter for the test strategy described on our software quality and testing page.

Insights

Further reading

All insights

FAQ

Frequently asked questions

Another question? Ask us

What is behaviour-driven development?

Behaviour-driven development (BDD) is a software development approach that describes the expected behaviour of an application through concrete examples. These examples are discussed between the business, developers and testers, then written as scenarios in the vocabulary of the business. The scenarios act as acceptance criteria and can be automated.

What do Given, When, Then mean?

Given, When and Then are the three keywords that structure a BDD scenario. In Dan North's article "Introducing BDD", Given sets an initial context, When describes an event and Then states the expected outcomes. The Gherkin language takes up these keywords and provides equivalents in other languages, including French.

How does BDD differ from TDD?

TDD (test-driven development) is a developer practice: write a failing test, then the code that makes it pass, then refactor. Dan North presents BDD as having grown out of his teaching of TDD, with the word "behaviour" replacing the word "test". BDD then extended to the expression of requirements, with scenarios written in the vocabulary of the business.

Does BDD require a tool?

BDD does not require a tool. Tools such as Cucumber or JBehave run scenarios written in plain language, but the Cucumber documentation states that BDD is not just a matter of using that tool. It identifies discovery, that is the discussion of concrete examples, as the practice to start with.

Who writes the scenarios in BDD?

The Cucumber documentation describes a collaborative writing of BDD scenarios, based on the examples discussed between business people and technical people. This joint writing establishes a shared language for talking about the system. A scenario written by developers alone remains a test, without the business agreement the approach seeks.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.