Behaviour Driven Development (BDD) is the natural evolution of test-driven development (TDD) that addresses challenges with poorly understood requirements, quality, and design. BDD uses examples written in a business-facing language to define requirements, automate functional tests, and improve communication between technical and business teams. BDD tests help improve software quality, design, and ensure requirements are fully implemented.

1. Behaviour Driven
Development
Introduction and Essence

2. Challenges
Poorly Understood requirements – What is meant by done?
Ensuring quality in changing code bases
Poorly Designed Software
How to implement Pull based processes like scrum
Test Reports don’t make much since to business stakeholders.
Poorly Designed Code/Classes/Components
Difficult to discover why a test has failed and analyse.

3. BDD Introduction
The Natural Evolution of Test Driven Development
Outside In
Pull based
Multi-Stakeholder
High-Automation
Agile

15. Manual Business Facing
Manual
Functional Tests
• User Story Tests
• Prototypes
• Simulations
Exploratory
Testing
• Usability Testing
• User Acceptance
Testing
• Alpha/Beta
Developer Tests
• Unit Tests
• Component Tests
Performance
and Load testing
• Security Testing
• Performance
Testing
• Load Testing
Technology Facing
Automated &
Supporting the Teams
Critique Product
Automated
Tools

18. Demo : BDD

20. Helps in
Communication
(At All Levels)

22. Helps Improve Design

23. Helps Fix Issues

24. Helps improve quality

25. Helps Define Done!

26. Helps Drive
Development