Chapter 5
Frequent Delivery and Visibility
Most software teams spend most of their time in an “in-progress” state, with the product only partially working, punctuated by occasional moments of “done” when deadlines hit. Teams using BDD can be in a stable done state multiple times per day. This creates opportunities for earlier and more frequent feedback from testers, product managers, stakeholders, and customers.
In this chapter, we look at the many ways a team’s behavior might change to take advantage of that more frequent delivery and increased visibility. We pay particular attention to how the tester’s role changes in BDD.
How BDD Changes the Tester’s Role
A good tester is a good questioner. What happens when the user starts from this context ...
Get Behavior-Driven Development with Cucumber: Better Collaboration for Better Software now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
