BDD
BDD (Behavior-Driven Development) is a practice for specifying and building software by the behavior its users should observe, written as plain-language scenarios that double as automated tests.
Dan North introduced BDD around 2006 as a refinement of 📝TDD (Test-Driven Development). His aim was to shift the conversation from "write a test first" to "describe the behavior first", in words that business people, testers and developers share. TDD asks whether a unit of code does what its author intended. BDD asks whether the system does what the people relying on it expect.
A BDD scenario follows a fixed shape: Given a starting context, When an event happens, Then an observable outcome follows. For example: given a lead who has unsubscribed, when the outreach loop runs, then no email is sent to them. Tools such as Cucumber read scenarios written in a structured format called Gherkin and run them against the system. The written specification is then also the regression suite.
BDD sits alongside acceptance test-driven development (ATDD) and Specification by Example, which share its outside-in approach. In practice the methods combine: BDD scenarios fix what the system must do from the outside, while TDD drives the code that makes each scenario pass.
I came across BDD as a term on 2026-11-20, and it named something we already do by instinct. TDD fits our dev system, where correctness lives in code. BDD fits our sales and agent systems, where what matters is how the system behaves toward people: who gets contacted, who gets held, what an agent says when asked.
