Automated testing turns formulated BDD scenarios into executable tests. Scenario tools invoke team-written automation code, making business-readable cases repeatable. section 1.3.4
Running relevant scenarios during development gives fast feedback and a safety net against regressions. Because the tests run during builds, they also help keep behavior documentation reliable. section 1.3.4 section 5.3.7
Figure 1.3 The BDD cycle is the outer loop – write a failing scenario, get the scenario to pass, then refactor. We enter the inner, TDD cycle to implement the code needed to move from a failing scenario to a passing scenario.

The cycle shows how a failing scenario guides implementation until it passes, followed by refactoring. section 1.3.4
A collected order
Automation code can prepare an order in the collected state to support a scenario stating that the customer's order has been collected. section 1.3.4



