Gherkin holds the promise of being an easy to implement and easy to understand tool for getting teams to be Test Driven. And it should be. But in our experience working with and coaching many teams, we have found significant differences between theory and practice. Too often, Gherkin scenarios result in test code that is difficult to understand, difficult to maintain, and not valuable. We will go over the following anti-patterns and discuss strategies to overcome them:
Scenarios that focus on UI implementation rather than expected behaviorScenarios that are too long and too...Raj Indugula
Introduced to agile methods via Extreme Programming in 2003, Raj Indugula is a Principal Coach at LitheSpeed with over 17 years of hands-on experience with the pragmatic application of agile methods and XP-inspired code quality practices, and coaching teams on the adoption of Lean-Agile-DevOps practices. He has helped develop all roles, from executive leadership to engineering teams, in lean software development, process frameworks, product ownership, and agile engineering and testing practices. His passion is helping organizations improve their software delivery game by working alongside teams and individuals within the context of their work. He is also a certified and accredited trainer for Scaled Agile Academy, Scrum Alliance, and ICAgile across a wide spectrum of agile process and technical courses.