Download as PDF, PPTX
Uploaded byDave Haeffner
Bdd lessons-learned
The document discusses the lessons learned from implementing behavior-driven development (BDD) at a company between 2012-2013. It describes introducing BDD practices like Gherkin and Cucumber, generating developer interest through coaching and automation of test scenarios. Challenges like lack of new automated tests and broken continuous integration were addressed. Over time, more robust BDD practices were established like standardized Gherkin formatting, production-like environments for specification workshops, and cross-browser testing. Key lessons highlighted are that writing good specifications is difficult, changing one thing at a time is best, and prioritizing test automation based on factors like frequency of change and business impact.
More Related Content
Similar to Bdd lessons-learned
Bdd lessons-learned
- 1. BDD Lessons Learned byDave Haeffner Monday, July 1, 13
- 2. Background & Primer Monday,July 1, 13
- 3. • Cucumber • SpecificationWorkshops • Selenium • Continuous Integration • A rabbit Potent potables Monday, July 1, 13
- 4. circa 2012/2013-ish BDDImplementation Monday, July 1, 13
- 5. circa 2012/2013-ish Introduced Gherkin Sold it,& coached it BDD Implementation Monday, July 1, 13
- 6. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it BDD Implementation Monday, July 1, 13
- 7. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Monday, July 1, 13
- 8. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Monday, July 1, 13
- 9. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Monday, July 1, 13
- 10. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Monday, July 1, 13
- 11. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Monday, July 1, 13
- 12. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Renewed Dev interest in automation Monday, July 1, 13
- 13. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Renewed Dev interest in automation Building Blocks Monday, July 1, 13
- 14. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Renewed Dev interest in automation Building Blocks Training Monday, July 1, 13
- 15. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Renewed Dev interest in automation Building Blocks Training Prod. like env’s & Spec. Workshops Monday, July 1, 13
- 16. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Renewed Dev interest in automation Building Blocks Training Prod. like env’s & Spec. Workshops Staggered automation Monday, July 1, 13
- 17. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Renewed Dev interest in automation Building Blocks Training Prod. like env’s & Spec. Workshops Staggered automation Churn Monday, July 1, 13
- 18. circa 2012/2013-ish ID’d, autom., and demoed key scenarios Introduced Gherkin Soldit, & coached it Dev interest & CI Vacation BDD Implementation Shambles & Initial Recovery Gross gherkin, no new autom, & busted CI CI notifications, standardized gherkin process Churn Churn Autom. & demo of critical funct. Renewed Dev interest in automation Building Blocks Training Prod. like env’s & Spec. Workshops Staggered automation Churn Cross- browser testing implem. Monday, July 1, 13
- 19. Some good questions toask yourself Monday, July 1, 13
- 20. • How oftendoes it need to be checked (e.g. how often does it change)? • How long does it take to test manually? • How valuable is it (e.g. core functionality that is used heavily by our users, used by a prominent user group, legal or political, etc.)? • How risky is the feature (e.g. fundamental back-end changes, complex architecture, large user facing impact)? • What is the level of effort to automate (S, M, L, XL)? • Does it involve look and feel? Monday, July 1, 13
- 21. • Where doesthe business logic live? • How is it architected? • What kind of test coverage exists already? Monday, July 1, 13
- 22. BDD Lessons Learned •Writing good gherkin is difficult • If you plan to change behavior, change one thing at a time • Top down doesn’t matter as much as bottom up • Ask good questions Monday, July 1, 13
- 23.
- 24.