liveBook · Manning

Chapter 1: What is BDD?

What you will learn in chapter 1 of Effective Behavior-Driven Development

This introduction presents BDD as a way to turn an evolving conversation about business needs into a guide for development, while clarifying that BDD is not primarily about testing.

After this chapter you will be able to

Section by section

Introduction

This introduction presents BDD as a way to turn an evolving conversation about business needs into a guide for development, while clarifying that BDD is not primarily about testing.

Key terms: socio-technical conversation, Behavior-Driven Development, precise, testable, Test-Driven Development, automated tests

1.1 The missing links between business needs and software delivery

This section frames the persistent gap between business needs and software delivery as a set of challenges spanning the development process.

Key terms: business problems, customer’s needs, software delivery, maintainability

1.1.1 Insufficient requirements

This section explains why high-level stakeholder requirements need ongoing communication and management to become a solution that meets the stakeholder’s intentions.

Key terms: requirement, stakeholder, business representatives, delivery team, clarification, business context, rework, management of requirements

1.1.2 Unreliable documentation

This section explains why maintenance becomes difficult when documentation and tests do not reliably connect delivered behavior to current stakeholder needs.

Key terms: maintainability, regression tests, unintended side-effects, stakeholder needs, current requirements, functional regression test, reverse engineer, automated link

1.1.3 Slow feedback

This section explains how delayed, unreliable, or unclear feedback about system behavior creates rework and delays, and why teams need earlier, meaningful results.

Key terms: feedback loops, manual regression tests, context-switching, flaky test, meaningful diagnostic information, granularity of the requirement

1.2 Origins of BDD

This section explains how BDD grew out of TDD to keep tests connected to expected business behavior and understandable to business people.

Key terms: Behavior Driven Development (BDD), Test Driven Development (TDD), collaboration, Test-Driven Development (TDD), Red, Green, refactoring, expected behavior, business requirements, business-readable

1.3 How BDD works

This section explains how each user story moves through discovery, formulation, and automation to contribute to working software.

Key terms: discovery, formulation, automation, examples, business-readable scenarios, user stories, stakeholders, requirements, working software, production code

1.3.1 Start with a user story

Introduces a user story as a starting point for conversation, with candidate rules that give initial scope but need scrutiny during discovery.

Key terms: user story, placeholder for a conversation, candidate rules, rule, discovery

1.3.2 Discovery

Discovery uses a team requirements workshop to turn a user story into concrete examples and a shared understanding of what should be delivered.

Key terms: discovery, requirements workshop, structured conversation, examples, rules, shared understanding, detailed requirements, story

1.3.3 Formulation

This section explains how formulation turns discovery examples into business-readable scenarios that specify required behavior, and why teams do it separately from discovery.

Key terms: formulation, discovery, business-readable scenario, required system behavior, Given, When, Then, Gherkin, scenario, delivery team

1.3.4 Automation

This section explains how teams automate formulated scenarios to guide implementation, get fast feedback, and keep specifications connected to working software.

Key terms: scenario automation tool, step, automation code, red, green, refactoring, TDD, rule, fast feedback, safety net

1.3.5 Testing

This section explains how BDD changes the focus of testing while preserving testers’ expertise and the need for human verification.

Key terms: BDD, agile testing, code quality, test automation, discovery, domain knowledge, cross-skilling, verification, manual regression testing, exploratory verification

1.3.6 BDD is a bridge

This section explains how discovered, formulated, and automated examples connect stakeholder requirements to delivered software throughout the system’s life.

Key terms: discovery, formulated, automated, executable verification, side effects, regressions, persistent documentation, maintainability

1.4 Common challenges when adopting BDD

This introduction notes that widespread BDD adoption does not guarantee success and previews a discussion of common challenges.

1.4.1 Naming is hard

This section explains why teams should focus on the techniques behind BDD rather than debates over names for similar approaches.

Key terms: Acceptance Test Driven Development (ATDD), Behavior Driven Development (BDD), Specification by Example (SbE)

1.4.2 BDD without the business

This section explains why BDD loses much of its value without business stakeholder involvement, and when a Product Owner can represent that perspective.

Key terms: business people, delivery team, iterative refinement of specifications, business-readable language, Product Owners, business stakeholder

1.4.3 Automation in isolation

This section explains why automating BDD scenarios without business and developer collaboration delivers limited value.

Key terms: automation in isolation, scenarios, system specifications, low-level automation steps

1.4.4 Unreadable documentation

Unreadable scenarios undermine the value of BDD specifications for business people and customers.

Key terms: scenarios, specification, formulation, business-readable language

1.4.5 Unmaintainable automation

This section explains why BDD scenario automation code needs to be both understandable and maintainable.

Key terms: scenario automation, automation code, idiomatic usage of natural language

1.5 Will AI make BDD irrelevant?

The section argues that AI may change software development, but BDD remains valuable for guiding AI-generated work with human domain knowledge, specifications, context, and controlled practices.

Key terms: specifications, guardrail, business-readable software specifications, domain knowledge, context, guidance, harness, small steps, process adherence, coding or design standards

1.6 How to begin implementing BDD

This section defines BDD in terms of examples and scenarios and cautions against adopting it faster than an organization can support.

Key terms: Behavior Driven Development, business requirements, illustrative scenarios and examples, commitment, investment, change, agile “transformations”

1.6.1 Evolution, not revolution

The section recommends introducing BDD through small, collaborative experiments that begin with business needs and discovery rather than an organization-wide rollout.

Key terms: experiment, proof of concept, iterations, business needs, user stories, discovery, formulation, automation, interfaces between different roles, collaboration

1.6.2 Collaboration

This section defines collaboration as meaningful, respectful exchange and argues that roles may need to change to make it possible.

Key terms: collaboration, meaningful interaction, exchange of useful information, role descriptions, organizational structure, roles and responsibilities, product owner, delivery team

1.6.3 Opinions have context

This section explains why claims that BDD failed need context and gives criteria for judging whether a software-development approach is worth adopting.

Key terms: BDD, team buy-in, configurable to your context, demonstrably delivers value

1.6.4 Free lunch or silver bullet?

BDD can improve software delivery, but adopting it takes sustained collaboration and technical care, and it cannot solve every problem.

Key terms: BDD, discovery, formulation, automation, code quality, silver bullet, less waste, fewer defects, reduced rework, faster feedback

1.7 Summary

Where this is used later

Concepts explained in this chapter

Chapter 2: Structured Conversation →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.