1. C UCUMBER behavior driven development Presented by: Julian Togashi and Ryan Lewis CPSC 473

2. Why Cucumber?  Software begins as an idea  Solves a problem  Makes an improvement  Brings products to market  Ideas must be communicated  Challenge – domain specific jargon  Challenge – differing technical understanding  Challenge – fuzzy details  High cost of failure  $$$  Frustration  Risks

3. Why Cucumber?  Goal  Breaking down communication barriers  Clients become active participants  Remove ambiguity  Behavior driven development  Agile processes / XP Test Driven Development  Acceptance Testing  Implementation  User stories  Executable specifications (Gherkin)  Language specific steps

4. The Process User Story stakeholders Feature(s) feature file Scenarios Step Definition Key Examples Steps Given – When - Then

5. An Example

9. Revised Steps

10. All Systems Go