Getting Past the 50+70=120 Calculator in Cucumber: 12 Things to Work On
With the best of intentions, people have flocked to Behavior Driven Development by way of Cucumber over the past few years, and that’s a great thing! But just like dieting, where great things can fall to the wayside from the temptation to indulge in wonderful desserts, BDD can fall to the wayside due to pressure to deliver more and more functionality Sprint over Sprint. Many times, Cucumber becomes just a way to automate a bunch of tests, which isn’t bad by itself, even if it doesn’t get to the core of how Product Owners and the Delivery Team should start to communicate. But without constant attention, that great garden of creeping Cucumber vines becomes a tangled mess that slowly withers away under massive technical debt.
Howard will guide you through 12 of the most important issues to work on in your garden of executable requirements. We’ll discuss and explore topics ranging from the easy to comprehend (such as imperative versus declarative style) to the difficult to deliver (such as how to keep Gherkin driven Selenium WebDriver tests working dependably through the use of advanced ExpectedCondition techniques). By the end of the session, you should have plenty to indulge in on a healthy diet of BDD!
Outline/Structure of the Talk
This session will discuss 12 common issues that people can improve on when developing with Cucumber, with special emphasis on techniques to employ when attempting to use Selenium WebDriver. The emphasis will be on craftsmanship and keeping technical debt low, so the automation suites can grow with the least amount of drag.
After the discussion of the 12 items, there will be a live demo of about 4 of the items, so people can actually experience what was talked through. I want to leave people with enough momentum of "getting it" that they will immediatly apply the patterns of goodness to their own work!
A much better understanding on how to employ "The 3 Amigos" to define executable requirements and iteratively implement both the code and the automated tests that support it.
Members of "The 3 Amigos", Software Developers, QA Testers