chapter one

1 What is BDD?

 

This chapter covers

  • Key challenges facing current software development processes
  • The three practices of Behavior Driven Development (BDD)
  • The relationship between BDD and Test-Driven Development (TDD)
  • Common challenges and solutions when adopting a BDD approach

It’s tempting to think of software development as a purely technical task—writing code to instruct a machine. In reality, software is the product of an ongoing socio-technical conversation among users, business stakeholders, and the delivery team. That conversation evolves over time, and the challenge is to capture it in a form that is precise, testable, and useful as a guide for building the system. This is the central goal of Behavior-Driven Development, or BDD.

BDD originated in the mid-2000s to help align technical practices more closely with business needs. Today, it is supported by a mature ecosystem of tools such as Cucumber, Reqnroll, and Behave, alongside nearly two decades of hard-earned lessons from practitioners.

1.1 The missing links between business needs and software delivery

1.1.1 Insufficient requirements

1.1.2 Unreliable documentation

1.1.3 Slow feedback

1.2 Origins of BDD

1.3 How BDD works

1.3.1 Start with a user story

1.3.2 Discovery

1.3.3 Formulation

1.3.4 Automation

1.3.5 Testing

1.3.6 BDD is a bridge

1.4 Common challenges when adopting BDD

1.4.1 Naming is hard

1.4.2 BDD without the business

1.4.3 Automation in isolation

1.4.4 Unreadable documentation

1.4.5 Unmaintainable automation

1.5 Will AI make BDD irrelevant?

1.6 How to begin implementing BDD

1.6.1 Evolution, not revolution

1.6.2 Collaboration

1.6.3 Opinions have context

1.6.4 Free lunch or silver bullet?

1.7 Summary