Introduction to BDD - shortened
2 likes8,739 views
The document discusses the challenges of maintaining high-quality software products, emphasizing that business needs are often poorly understood by both stakeholders and developers, leading to low-quality outputs. It outlines three essential practices for successful projects: discovery through collaboration, formulation of examples using business terminology, and automation of documentation to ensure ongoing verification of system behavior. Additionally, it provides specific scenarios related to team scoring, demonstrating the structured approach to requirements gathering and testing.
Introduction to BDD - shortened
- 1. @sebrose http://cucumber.io Seb Rose Can we reduce the stress of maintaining a high quality product?
- 2. @sebrose http://cucumber.io How Projects Really Work (version 1.5) Create your own cartoon at www.projectcartoon.com How the customer explained it How the project leader understood it How the analyst designed it How the programmer wrote it What the beta testers received How the business consultant described it How the project was documented What operations installed How the customer was billed How it was supported What marketing advertised What the customer really needed www.projectcartoon.com
- 3. @sebrose http://cucumber.io Business needs are not well understood by the people who want the software
- 4. @sebrose http://cucumber.io Business needs are not well understood by the people who want the software
- 5. @sebrose http://cucumber.io Business needs are not well understood by the people who will deliver and test the software
- 6. @sebrose http://cucumber.io Business needs are not well understood by the people who will deliver and test the software
- 7. @sebrose http://cucumber.io Business needs are not well understood by the people who will deliver and test the software
- 8. @sebrose http://cucumber.io The software is low quality with lots of bugs
- 9. @sebrose http://cucumber.io The cost of change over time increases rapidly CostofChange Time
- 12. @sebrose http://cucumber.io Successful Projects Shared understanding Know when youare done
- 13. @sebrose http://cucumber.io Successful Projects Shared understanding Know when youare done Know what to do next
- 14. @sebrose http://cucumber.io Successful Projects Shared understanding Know when youare done Know what to do next The codebase supports the inevitable changes as theproject evolves
- 15. @sebrose http://cucumber.io Successful Projects Shared understanding Know when youare done Know what to do next The codebase supports the inevitable changes as theproject evolves Know quickly when new changes break existing behaviour
- 17. @sebrose http://cucumber.io Discovery Create a shared understanding of the requirements through collaboration, typically achieved through a structured conversation centred on rules and examples Three practices
- 18. @sebrose http://cucumber.io Discovery Create a shared understanding of the requirements through collaboration, typically achieved through a structured conversation centred on rules and examples Formulation Examples of system behaviour are documented using business terminology Three practices
- 19. @sebrose http://cucumber.io Discovery Create a shared understanding of the requirements through collaboration, typically achieved through a structured conversation centred on rules and examples Formulation Examples of system behaviour are documented using business terminology Automation The documentation is automated, creating living documentation that verifies the system’s behaviour Three practices
- 20. @sebrose http://cucumber.io Discovery Create a shared understanding of the requirements through collaboration, typically achieved through a structured conversation centred on rules and examples Formulation Examples of system behaviour are documented using business terminology Automation The documentation is automated, creating living documentation that verifies the system’s behaviour Three practices
- 22. @sebrose http://cucumber.io Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50 Formulation
- 23. @sebrose http://cucumber.io Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50 Formulation
- 24. @sebrose http://cucumber.io Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50 Formulation
- 25. @sebrose http://cucumber.io Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50 Formulation
- 26. @sebrose http://cucumber.io Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50 Formulation
- 27. @sebrose http://cucumber.io Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50 Formulation
- 28. @sebrose http://cucumber.io Feature: Team Scoring Teams start with zero score. Correct answer gets points depending on how difficult it is. Scenario: Score starts at 0 Given I register a team Then my score is 0 Scenario: Correct easy answer scores 10 Given I register a team When I submit a correct easy answer Then my score is 10 Scenario: Correct hard answer scores 50 Given I register a team When I submit a correct hard answer Then my score is 50 Formulation
- 34. @sebrose http://cucumber.io Features -Scenarios -Steps -Gherkin Each scenario is an example Automation
- 35. @sebrose http://cucumber.io Features -Scenarios -Steps -Gherkin Glue code Each scenario is an example Automation
- 36. @sebrose http://cucumber.io Features -Scenarios -Steps -Gherkin Glue code -Step definitions Each scenario is an example Automation
- 37. @sebrose http://cucumber.io Features -Scenarios -Steps -Gherkin Glue code -Step definitions -Java / C# Each scenario is an example Automation
- 38. @sebrose http://cucumber.io Features -Scenarios -Steps -Gherkin Glue code -Step definitions -Java / C# Automation
- 39. @sebrose http://cucumber.io Features -Scenarios -Steps -Gherkin Glue code -Step definitions -Java / C# Automation
- 40. @sebrose http://cucumber.io Features -Scenarios -Steps -Gherkin Glue code -Step definitions -Java / C# Application Automation
- 41. @sebrose http://cucumber.io Pulling it all together
- 43. Seb Rose Twitter: @sebrose Blog: http:/cucumber.io/blog E-mail: seb@cucumber.io