Cucumber Tests: Legends and Reality

on YouTube ↗16m

" summary

A Java project for a financial curve engine used Cucumber with Gherkin scenarios, IntelliJ plugins, Jenkins reports and Cucumber Studio to store scenarios supplied by the client (50 pages, ~30 business rules). The implementation produced ~40–50 step definitions, 60 scenarios and 300+ data rows (~1,500 step executions per run) and proved effective for validating complex business rules but costly to author step definitions and to set up integration, so it is not suited to unit or short-run integration testing.

AI-written summary · about

" chapters (12)

1. 0:00Start
2. 0:29What is Cucumber?
3. 0:59Behavior Driven Development
4. 1:46User Expectations
5. 2:42Concrete Case: Project Presentation
6. 3:19Product Curve
7. 3:53Interactions with the Client
8. 4:28The Journey
9. 6:08Feature File
10. 7:27Missing Step Definitions
11. 8:52Command Line Output
12. 9:18Feedback

" related talks

• 44mBDD with JUnit 5 and CucumberCatalin Tudose · Conf42 Enterprise Software 2021
• 37mCucumbers Have Layers: A Love StorySam Livingston-Gray · RubyConf 2015
• 36mBDD With CucumberGooi Liang Zheng · RubyConf MY 2017
• 35mCucumber: Automating the Requirements Language You Already SpeakBen Mabey · Agile Roots 2010
• 40mHow Cucumber Can Improve Your TestingTitus Fortner · Selenium Conference 2013
• 16mBDD with cucumber.jsRyan Marsh · Assert(js) 2018
• 34mWriting end to end tests with a smileEkaterina Budnikov, Kim Hogeling · GDG DevFest Hamburg 2017
• 30mBehavior driven integration with Cucumber and CitrusChristoph Deppisch · Devoxx Belgium 2017