The document discusses Behavior-Driven Development (BDD) using Cucumber, emphasizing communication and collaboration among team members to enhance automation and documentation processes. It outlines the test pyramid, detailing various testing levels and the importance of defining specifications through examples. The conclusion highlights that preparation and collaboration are essential for building trust and achieving long-term value in software development.

1. BDD With Cucumber
MÜCAHİT KURT
Sn. Project Manager @ INNOVA
@mucahitkurt

2. Mücahit KurtSn. Project Manager
@mucahitkurt
@mucahitkurt
@mucahitkurt
mucahit.blogspot.com.tr
2

3. Test Pyramid
3
GUI Tests
API Tests
Integration Tests
Component Tests
Unit Tests
Manuel
Tests
GUI Tests
API Tests
Integration Tests
Component Tests
Unit Tests
Manuel Tests
How it should be done What many teams do

4. BDD Concept
“Using examples in conversation to illustrate behaviour.”
4
Specification by Example
Acceptance TDD
Extented TDD BDD

5. Why BDD?
5
Communication
Collaboration
Automation
Living Documentation

6. Traditional
6
Analyst Developer
Tester
Deployment
Bug Report
Requirements
Clarify

7. Collaboration
7
Analyst
Developer
Tester
Deployment
Bug Report
Requirements
Clarify
Specifications
Developer Analyst
Three Amigos
Tester

8. Cucumber is the Tool
8
Features
Scenarios
Steps

9. Cucumber
9
Your Project
Features
Scenarios
Steps
Step Definitions
Support Code
Automation Library
Your System
Business
Facing
Technology
Facing

10. Sample Feature
10
Language
Feature
Scenario
Steps

11. Gherkin is the Language
11
Cucumber supports over 60 spoken languages.

12. Step Definitions
12

13. Regular Expressions
13
http://regexr.com

14. How it Works?
14
Execute
Scenario
Read First Step
Do we have a matching
step definition?
Execute Step
Definition Code
Block
Was an
exception
thrown?
Any more
steps?
Passed Scenario Failed Scenario
Pending
Scenario
Undefined
Scenario
Pending
Read next step
No
Yes
No
No
Yes
No
Yes
Yes

15. Expressive Scenarios
Background, Data Table, Scenario Outline, Tag, Hook
15

16. Outside-in
16
Failing
Acceptance
Test
Failing
Unit
Test
Make it
Pass
Refactor

17. 17
Exercise

18. Keeping Your
Cucumbers Sweet
Don’t forget the test pyramid
Work together
Care your tests & codes
18

19. Environment
Parallel Run
19
Jenkins-Plugin-Parallel Run
Reporting
Different sets with tags
Spring, Pico-Container, Selenium etc. support

20. Conclusion
Collaboration on requirements builds trust between
stakeholders and delivery team members
Collaboration requires preparation
Looking at the end goal as business process
documentation is a useful model
Long-term value comes from living documentation
20

21. References
The Cucumber For Java Book
By Seb Rose, Matt Wynne, Aslak Hellesoy
Specification By Example
By Gojko Adzic
21

22. End of the Fun
22

23. Credits
23
• Three feathers by Deb, https://www.flickr.com/photos/25154062@N02/5522723111/
• analyst by Gregor Črešnar from the Noun Project
• percentage by Gregor Črešnar from the Noun Project
• Money by Gregor Črešnar from the Noun Project
• Value by Gregor Črešnar from the Noun Project
• Search by Luis Prado from the Noun Project
• User by Wilson Joseph from the Noun Project
• bug by Robert Bjurshagen from the Noun Project
• cycle by Robert Bjurshagen from the Noun Project
• Checklist by Davo Sime from the Noun Project
• question-mark by Cris Dobbins from the Noun Project
• Cross by Zaff Studio from the Noun Project
• Back-ache !!!!!!!!!!! by Craig Sunter, https://www.flickr.com/photos/16210667@N02/9046360969
• Lemur up there by Tambako The Jaguar, https://www.flickr.com/photos/tambako/13662196145/