The document discusses using human-readable stories and scenarios to define acceptance criteria for software features. It presents a format for writing stories with scenarios in plain text, and shows how the RSpec testing framework can be used to programmatically bind the plain text stories and scenarios to automated tests. The stories follow a Given-When-Then structure and allow non-technical users and developers to communicate acceptance criteria using a shared language and format.

1. http://citconf.com/amsterdam2008/ User Acceptance Testing Driven by Humans telling Stories (with RSpec) Jean-Michel Garnier | 21croissants.com

3. QA Biz Analyst Ruby on Rails web app $sel.click('foo') wait_for('x$%¬') The user wants something for sure but I have no clue if developpers can implement it or not... User story As a User I want ... Scenario 1 Scenario 2 end user developper

4. Rspec runs “plain text” Stories Story: Logging in As an anonymous user I want to login So that I can ... Scenario: 1. When she goes to the page '/login' ... same jargon! end user developper

11. Binding plain text / RSpec Given she goes to the page ' /login '

12. More binding

14. Demo

15. Philippe Hanrigou reports