![Have enough conversation to get started.
Find out where the riskiest bits are and
where the system behaves unusually .
Chat, Discuss, Discover, Work out how and
when , you are going to get feedback on the
work you are about to do . Then and only
then , reach for tools
[ Liz Keogh]](https://image.slidesharecdn.com/bddwithcucumber1-160411133626/85/Introduction-to-Bdd-and-cucumber-10-320.jpg)
![Story
• What are we really trying to build ?
• It has to be a description of a requirement and its business benefit, and a
set of criteria by which we all agree that it is “done” [Dann North]
• Written in business language
• Stories are the result of conversations between the project stakeholders,
business analysts, testers and developers
Example
As a user
I want to publish a tweet
So that share information with my followers](https://image.slidesharecdn.com/bddwithcucumber1-160411133626/85/Introduction-to-Bdd-and-cucumber-11-320.jpg)
![Scenario
• Is set of conditions that story must meet for it to be accepted as complete
• Can be used to help discover the scope of the story or the feature
• Is not replacement for conversation
• Is the outcome of conversations with all players
• Scenario title should say what’s different
• The scenario should be described in terms of Givens, Events and Outcomes
Given [some context]
When [I do something]
Then [this happens]](https://image.slidesharecdn.com/bddwithcucumber1-160411133626/85/Introduction-to-Bdd-and-cucumber-12-320.jpg)
![Gherkin
Means : “a small variety of cucumber, or a young green cucumber used for
pickling.” [google]
Cucumber executes .feature files, and those files contain executable
specifications written in a language called Gherkin.
Gherkin supports 60+ languages.
Gherkin is designed to be easy to learn by non-programmers, yet
structured enough to allow concise description of examples to illustrate
business rules in most real-world domains. [www. cucumber.io]](https://image.slidesharecdn.com/bddwithcucumber1-160411133626/85/Introduction-to-Bdd-and-cucumber-18-320.jpg)
![References
• http://dannorth.net
• http://lizkeogh.com
• http://behaviour-driven.org
• https://cucumber.io
• BDD in action [John Ferguson]
• The cucumber book [Matt wynne and Aslak Hellesoy]](https://image.slidesharecdn.com/bddwithcucumber1-160411133626/85/Introduction-to-Bdd-and-cucumber-25-320.jpg)
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Introduction to Bdd and cucumber (20)
Ad
Recently uploaded (20)
Introduction to Bdd and cucumber
- 1. Introduction to BDD with Cucumber Nibu baby
- 4. An Evolution TDD ATDD BDD
- 6. BDD • Uses examples to illustrate behavior • Core is around conversations and requirements discovery • Uses conversations around examples, expressed In a form that can be easily automated, to reduce lost information and misunderstandings • Starting with the business outcome, and working through high level functional areas to drill into specific stories with acceptance criteria. • When writing examples, regression tests are a by-product
- 7. Examples Given a context When an event happens Then an outcome should occur
- 10. Have enough conversation to get started. Find out where the riskiest bits are and where the system behaves unusually . Chat, Discuss, Discover, Work out how and when , you are going to get feedback on the work you are about to do . Then and only then , reach for tools [ Liz Keogh]
- 11. Story • What are we really trying to build ? • It has to be a description of a requirement and its business benefit, and a set of criteria by which we all agree that it is “done” [Dann North] • Written in business language • Stories are the result of conversations between the project stakeholders, business analysts, testers and developers Example As a user I want to publish a tweet So that share information with my followers
- 12. Scenario • Is set of conditions that story must meet for it to be accepted as complete • Can be used to help discover the scope of the story or the feature • Is not replacement for conversation • Is the outcome of conversations with all players • Scenario title should say what’s different • The scenario should be described in terms of Givens, Events and Outcomes Given [some context] When [I do something] Then [this happens]
- 13. BDD tools Few of them ….
- 15. Cucumber • Collaboration tool • It’s Testing tool • Outside-In approach , where programmers incrementally write code and run the scenarios using Cucumber until the feature passes all the tests • Supports about 60+ languages • Helps to execute plain text functional descriptions as automated tests • Automation can be written in own favorite language ( Ruby, Java, c#.net , JavaScript, Scala, Groovy, Jython, Python, Perl, Go, C++ etc) • writing scenarios before code enables programmers to be guided by an unambiguous specification
- 17. Life cycle Define steps Run and watch it fail Write code Refactor Add Scenarios
- 18. Gherkin Means : “a small variety of cucumber, or a young green cucumber used for pickling.” [google] Cucumber executes .feature files, and those files contain executable specifications written in a language called Gherkin. Gherkin supports 60+ languages. Gherkin is designed to be easy to learn by non-programmers, yet structured enough to allow concise description of examples to illustrate business rules in most real-world domains. [www. cucumber.io]
- 20. Gherkin Keywords • Feature • Scenario • Given, When, Then, And, But • Background • Scenario Outline • Examples More helpful keywords • """ (Doc Strings) • | (Data Tables) • @ (Tags) • # (Comments)
- 21. Cucumber testing stack Project Features Scenarios Steps Steps Definitions Automation code support System Business Facing Technology Facing
- 22. Let’s explore
- 23. Benefits • Better communication • Ubiquitous language ( Same/being present everywhere ) • Better collaboration between stakeholders, BA, QA and Developers • Formal documentation is not required • Living Documentation (Single source of truth) • Quick feedback (If the automated tests are included in the CI) • Right Focus, Right Product, Product Right
- 24. Disadvantages • It requires high level of business engagement and collaborations • May not work well in silos • Poorly written tests can lead to higher test-maintenance costs
- 25. References • http://dannorth.net • http://lizkeogh.com • http://behaviour-driven.org • https://cucumber.io • BDD in action [John Ferguson] • The cucumber book [Matt wynne and Aslak Hellesoy]