BDD (behavior-driven development) is a software development practice in which the behavior a system should exhibit is first described as concrete examples that both business stakeholders and developers can read, and those examples then serve as automated tests that drive implementation. It was proposed in the mid-2000s by Daniel Terhorst-North as an attempt to make TDD easier to explain and adopt.
Examples are usually written in a Given-When-Then format, and tools such as Cucumber and JBehave connect these sentences to executable tests. Together with TDD, ATDD, and Specification by Example, it belongs to the family of practices that use examples to capture requirements and tests.