Keeping your Cucumbers Sweet
This extract from The Cucumber for Java Book distils many years of experience gained by the Cucumber team. In it they describe the challenges that they’ve seen their customers struggle with when using Cucumber as part of their development process and give detailed advice and instructions to help you avoid these problems from the start. If all your team members (including your business representatives) read this chapter BEFORE you start writing scenarios you’ll be well prepared to get maximum value from your executable specification for minimum effort.
- Writing scenarios using Cucumber is easy, but it takes skill and effort to keep them maintainable and readable.
- Speed of feedback is usually more important than exhaustive coverage.
- Consistent results are essential, so invest in fixing ‘flaky’ scenarios
Seb Rose, Claysnow, UK
Consultant, coach, designer, analyst and developer for over 30 years.
Seb has been involved in the full development lifecycle with experience that ranges from Architecture to Support, from BASIC to Ruby. Recently he has been helping teams adopt and refine their agile practices, with a particular focus on automated testing.
Regular speaker at conferences and occasional contributor to software journals. Contributing author to “97 Things Every Programmer Should Know” (O’Reilly) and lead author of The Cucumber for Java Book (Pragmatic Programmers).
Matt Wynne, co-founder Cucumber Ltd
Matt is a leading BDD practitioner, a member of the Cucumber core team, and a programmer, coach, trainer, and popular international speaker. Alongside Aslak Hellesøy and Julien Biezemans, Matt is co-founder of Cucumber Ltd., the company behind Cucumber.
Aslak Hellesøy is the creator of Cucumber. During his career Aslak has worked with both small and large organizations in industries such as telecom, trading, insurance, car manufacturing, education, and government. Aslak is co-founder of Cucumber Ltd, the company behind Cucumber.