Learn the basics of behavior-driven development (BDD). Discover how BDD can improve collaboration, refine requirements, and identify defects earlier in the software testing cycle.
- If you're a part of an Agile organization, you're already aware of the benefits of collaboration between teams to facilitate building features that hold value for your business stakeholders. But a lack of understanding around the requirements, what should be built, can still occur. Have you ever experienced getting to the end of an iteration only to discover that miscommunications caused you to build out a feature that didn't provide value? Hi, I'm Robin Beck, and in this introduction to behavior-driven development, we'll explore some of the benefits of the BDD process by highlighting how the philosophy can clarify details that often get lost during software development.
We'll investigate the basics of how using a BDD framework, like Cucumber, can provide readable acceptance criteria, improved collaboration, and identity defects earlier in the testing life cycle. Let's dive in.
- What is behavior-driven development?
- Agile and BDD
- BDD examples
- BDD frameworks
- Defining scenarios
- Domain modeling
- Enforcing object-oriented design
- BDD process: Behavior before function