Behavior-Driven Development

Course details

Behavior-driven development (BDD) emerged from test-driven development as a process that enhances collaboration with non-technical teams. BDD tests are focused on the user and system behavior, and can clarify details that are often lost during the traditional software development process. This training course teaches the basics of behavior-driven development. Learn how BDD fits in an agile workflow, how to drive BDD process within a team, and the basics of using popular BDD frameworks like Cucumber. Instructor Robin Beck helps you get hands-on with Cucumber and its specification language, Gherkin, providing examples of writing requirements specifications, defining scenarios, setting up failing tests, and optimizing your code to emphasize domain-driven and object-oriented design. He wraps up with some best practices for implementing behavior-driven development and keeping the philosophy—behavior over function—at top of mind.

Learning objectives
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

Concepts

0. Introduction

01 - Collaboration with behavior-driven development (BDD)
02 - What you should know
03 - Getting set up

1. Behaving Agilely

04 - Agile in context
05 - TDD historically
06 - Why is BDD so compelling
07 - Case study conclusions
08 - Building the right thing
09 - Concrete example

2. Give Me an Example

10 - Three amigos meeting
11 - The three amigos in action
12 - Gherkin specifications
13 - Translate the scenario into Gherkin

3. Hands On with Cucumber

14 - BDD frameworks
15 - The emergence of Cucumber
16 - Set up the caffeinate project
17 - Define the scenario
18 - Model the domain
19 - Embracing failure
20 - Objectify the application
21 - Add a second scenario

4. Remember the Process

22 - Review
23 - Behavior before function

Conclusion

24 - Next steps

Behavior-Driven Development

Authors

Robin Beck