Behaviour Driven Development

From Glitchdata
Jump to navigation Jump to search

Behaviour Driven Development (BDD) is a test-first approach to writing requirements. It encourages teams to use conversation and concrete examples to formalise a shared understanding of how the application should behave. It emerged from test-driven development (TDD).

  • BDD -> TDD
  • Use Gherkin syntax (Given-When-Then) is commonly used
  • Permits building executable specifications
  • Acceptable criteria become executable tests

Behavior-driven development combines the general techniques and principles of TDD with ideas from domain-driven design and object-oriented analysis and design to provide software development and management teams with shared tools and a shared process to collaborate on software development.

Although BDD is principally an idea about how software development should be managed by both business interests and technical insight, the practice of BDD does assume the use of specialized software tools to support the development process.[5] Although these tools are often developed specifically for use in BDD projects, they can be seen as specialized forms of the tooling that supports test-driven development. The tools serve to add automation to the ubiquitous language that is a central theme of BDD.