Review
“”There are many cookbooks but very few “chef books.” Cucumber Recipes is inspiring enough to qualify as a chef book. If there’s a will and a desire to use Cucumber in the process, Cucumber Recipes will more than likely show you a way…or many ways! From the basic to the esoteric, there’s something for everyone in Cucumber Recipes.””–Michael Larsen, Senior quality assurance engineer, SocialText
“”If you’re automating tests of any kind using Cucumber, in any language, against any type of software, you need this cookbook. Its recipes will help you write useful, easily maintained tests for even the most puzzling scenarios. Like all good cookbooks, it teaches good techniques and principles that will help you improve all your tests. Best of all, you can actually code the examples yourself, and learn by doing.””–Lisa Crispin, Co-author, “Agile Testing: A Practical Guide for Testers and Agile Teams”””
“”Cucumber Recipes has testing solutions for a variety of platforms. It is a powerful book that gives us useful tips to use BDD in our chosen environment. To realize the power of BDD, Cucumber Recipes is a must on every software test engineer’s table.””–Kavitha Naveen, Senior lead – quality engineering
From the Author
Q & A With Matt and IanQ. Why do you use Cucumber?Ian: I use it because it keeps my automated tests readable and usable, even years after I’ve written them.Q. Why did you decide to write this book?Matt: When Aslak and I wrote the first Cucumber Book, we wanted to include a selection of guides to using Cucumber in different situations. Once we started to write them, we realized there were so many different ways you can use Cucumber! That’s when we decided these guides deserved a whole book of their own.Q. How do you each use Cucumber in your jobs?Matt: I run an online collaboration tool called Relish that helps teams share their living documentation (written in Cucumber) with non-technical stakeholders. Of course, I use Cucumber on a daily basis to drive out new features for the product.I also work as a trainer and consultant, traveling to teams who want to use Behavior-Driven Development (BDD). I get to see a lot of the good and bad practices out there, and I get great feedback about how the tool is being used by people.Ian: I work at a test and measurement hardware company. We use a lot of different automation frameworks, but the projects that use Cucumber consistently have the most readable test cases–the kind that can be shared among engineering, marketing, and testing groups.Q. What’s in store for Cucumber in the future?Matt: We’re working on a new, faster parser, which will allow more customizable behavior such as running scenarios in random order.We’re aiming to make Cucumber’s core code more lightweight, with better APIs and extension points. This way, we can make Cucumber more powerful without adding a maintenance burden. I’d also like to see much better tools for running and reviewing features–maybe even monitoring a running Cucumber suite from your web browser!
About the Author
*Ian Dees* was first bitten by the programming bug in 1986 on a Timex Sinclair 1000, and has been having a blast in his software apprenticeship ever since. By day, Ian slings code, tests, and puns at a Portland-area test equipment manufacturer. By night, he converts espresso into programming books, including Scripted GUI Testing With Ruby and Using JRuby.
Matt Wynne 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. Matt tweets from @mattwynne and @cucumberbdd.
Aslak Hellesoy 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. He tweets from @aslak_hellesoy and @cucumberbdd.