Content tagged with: cucumber
Software tests never run fast enough. To improve this performance, this article presents a process called DMAIC (Define, Measure, Analyze, Improve, Control). It shows how to apply this approach with Cucumber, an open source Behavior Driven Development tool. Cucumber lets you describe how software should behave in plain text. The text is written in a business-readable domain-specific language and serves as requirements documentation and source of automated acceptance tests.
Gherkin is the language that was originally used to define tests in Cucumber, a tool that executes plain-text functional descriptions as automated tests. Acceptance criteria are an important element of agile specifications, but they are often used just vaguely or omitted completely.
Behavior-driven development (BDD) is similar to test-driven development (TDD), but the tests for BDD are written in an easier-to-understand language so that developers and clients alike can clearly understand what is being tested. In this article based on chapter 2 of Rails 3 in Action, the authors discuss two tools for BDD: RSpec and Cucumber.
Wouldn’t it be nice to have the Business Analyst write out the acceptance criteria in plain English, and then have those criteria run as tests? Join us for a beginner to intermediate walk through of Cucumber and Selenium. Learn how to write tests that are easy to understand and run. There will be plenty of examples and sample code to get you going in the right direction.
In this blog post, Adam Boas discusses the danger of using Behavior Driven Development (BDD) tools like Cucumber to build an automated regression suite.
This free book is a step-by-step guide for Cucumber, the open source ruby Behavior Driven Development tool.
Iain Hecker discuses the way to describe behavior in Cucumber compared to the simpler option provided by Steak. Cucumber and Steak are two open source ruby behavior driven development (BDD) tools.