Cucumber is a tool that uses plain English scenarios to define tests in a way that is readable for both technical and non-technical audiences. It supports behavior-driven development (BDD) by mapping scenarios written in a language called Gherkin to code via step definitions. This allows automating user stories and acceptance criteria while keeping documentation and code in sync. Cucumber reports provide a way to present test results from automated scenarios.

1. Cucumber Basics
PRASHANTH SAMS

2. Why Cucumber ?
 Living Documentation
 Focus on the Customer
 Less Rework on Automation World / Refactor
TDD
BDD
Acceptance
Testing
meets requirements
Open-source
User Stories

3. BDD Automation Architecture
•Gherkin
•Readable
Plain English
Text
•Step Definition
•Mapping
Interpreter
•Page Object
•Automation
Code
Your</CODE>

4. Insights
 Code free
 Readable to each and every contributors
 Code Refactor

5. Feature standards

6. Annotations
 Background
 Scenario
 Scenario Outline
 Given, When, Then, And, But
 Examples

7. Scenarios
• Scenario
• Scenario Outline

8. Hooks
 BeforeFeature
 BeforeTest
 Before
 After
 AfterTest
 AfterFeature
Reduce Code redundancy
Test setup/teardown
Test cleanup
Repetitive task

9. Automation Results with Tools

10. Cucumber HTML Report

11. Thank you!
@prashanthsams