BDD Automation Puzzlers
summary
Covers practical pitfalls and fixes in BDD test automation with JBehave and Cucumber: shows that running JBehave under TestNG needs a custom TestNG/JUnit runner, Cucumber disallows empty Example columns and empty-regex step definitions because they produce ambiguous-match exceptions, and a JBehave composite-step implementation can cause a StackOverflow when steps call each other. Presents a Levenshtein-distance based step collector to prioritize best step matches, includes code snippets and reproducible failure cases so the fixes can be verified.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:31JBehave with TestNG
- 8:31Simplify Cucumber scenarios
- 14:29Cucumber step order
- 19:21JBehave step priority
- 25:29JBehave @Composite
- 31:28Conclusion
related talks
16mBDD with cucumber.js
50mMake BDD great again
53mBehaviour Driven Development, BDD, with Cucumber for Java
44mBDD with JUnit 5 and Cucumber
36mBDD With Cucumber
23mBDD To The Bone: Acceptance Testing with Behave and Selenium
45mLet's talk about software behaviour (BDD)
01h 05mContrasting Test Automation and BDD: An "Interactions Over Tools" Perspective