Making a Better Salad: Behavior-Driven Development with Lettuce
Is your organization still using brittle GUI driven-tools to ensure applications can be tested? Do you find these difficult to map to the user stories that describe product owner/business needs? One of the current Agile practices to doing this is Behavior-Driven Development (aka Acceptance Test-Driven Development) and writing user stories and acceptance criteria in a Specifications by Example format. This has real power in that business people can understand the tests and the delivery team can ensure the code meets the tests, thus they serve as an example.
This tutorial will give a short background on Specs by Example/BDD and the show you how to write such tests in Lettuce. You will gain a deeper understanding of how you can apply this to writing your applications.
Agile testing with Grails, Spock, and GebBill Schneider
schedule 2 years agoSold Out!
Grails is already a great platform for agile software development. Developers using Grails can iterate rapidly, without the burdens of tedious Java EE syntax and server restarts. Yet the best part of using Grails in an agile environment may be the testing frameworks. In this session I will demonstrate two testing frameworks in Grails: Spock and Geb.
Spock brings BDD-like syntax (given, when, then) to tests, with support for running the same tests against different inputs and outputs. Geb simplifies writing functional (UI automation) tests, as a layer on top of the Selenium Web Driver. Geb makes UI automation more accessible to developers by embracing closures and jQuery-style selectors. Geb integrates fully in the Grails build cycle; the coverage report combines coverage across unit, automation, and functional tests. A team using both Geb and Spock can choose the best form of testing for each story, for example, isolating business logic with unit tests, and covering controller classes through end-to-end UI tests.