Writing runnable acceptance criteria in plain text with Cucumber.

1. Writing runnable acceptance criteria in plain text with Farooq Ali

2. The Yawning Crevasse of Doom

3. fluffy high-level needs

4. <technical_babble />

5. [Test] [ExpectedException(typeof(InsufficientFundsException))] public void TransferWithInsufficientFunds() { Account source = new Account(); source.Deposit(200.00F); Account destination = new Account(); destination.Deposit(150.00F); }

7. the convergence of two movements

8. the convergence of two movements Behavior-Driven Development (BDD) & Domain-Specific Languages (DSLs)

9. “Acceptance criteria should be executable” “…a ubiquitous language for analysis” BDD movement

10. what are we really trying to describe?

11. what are we really trying to describe? the human concept of causality

12. Causality Precondition -> Given Action -> When Outcome -> Then

13. Causality Setup Data/State -> Given Call Method -> When Assert -> Then

14. “…a computer language that's targeted to a particular kind of problem, rather than a general purpose language that's aimed at any kind of software problem.” DSL movement

15. “The sweet spot, however is in making DSLs business-readable rather than business-writeable.” DSL movement

16. BDD + DSL

17. Gherkin Feature: Addition As a math moron I want to add two numbers together So that I can better use my scarce brain processing power Scenario: Adding positive numbers together Given I enter 1 into the calculator When I add 1 to it Then the calculator should show 2

18. Acceptance Criteria

19. Shared Vocabulary

20. Documentation

21. Traceability

22. Bug Tracking

23. Using Cucumber

24. Components Building Blocks Acceptance Criteria (Plain Text) Step Definitions (Ruby)

25. Acceptance Criteria Acceptance Criteria Feature: Addition As a math moron I want to add two numbers together So that I can better use my scarce brain processing power Scenario: Adding positive numbers together Given I enter 1 into the calculator When I add 1 to it Then the calculator should show 2

26. Acceptance Criteria Acceptance Criteria Feature: Addition As a math moron I want to add two numbers together So that I can better use my scarce brain processing power Scenario: Adding positive numbers together Given I enter 1 into the calculator When I add 1 to it Then the calculator should show 2

27. Acceptance Criteria Acceptance Criteria Feature: Addition As a math moron I want to add two numbers together So that I can better use my scarce brain processing power Scenario: Adding positive numbers together Given I enter 1 into the calculator When I add 1 to it Then the calculator should show 2

28. Acceptance Criteria Acceptance Criteria Feature: Addition As a math moron I want to add two numbers together So that I can better use my scarce brain processing power Scenario: Adding positive numbers together Given I enter 1 into the calculator When I add 1 to it Then the calculator should show 2

29. Acceptance Criteria Acceptance Criteria Feature: Addition As a math moron I want to add two numbers together So that I can better use my scarce brain processing power Scenario: Adding positive numbers together Given I enter 1 into the calculator When I add 1 to it Then the calculator should show 2

30. Keywords Keywords

31. Languages Languages Macintosh-9:calculator ThoughtWorks$ cucumber --language help | ar | Arabic | العربية | bg | Bulgarian | български | cat | Catalan | català | cy | Welsh | Cymraeg | cz | Czech | Česky | da | Danish | dansk | de | German | Deutsch | en | English | English | en-au | Australian | Australian | en-lol | LOLCAT | LOLCAT | en-tx | Texan | Texan | es | Spanish | español | et | Estonian | eesti keel | fi | Finnish | suomi | fr | French | français | he | Hebrew | עברית | hr | Croatian | hrvatski | hu | Hungarian | magyar | id | Indonesian | Bahasa Indonesia

32. Step Definitions Building Blocks Given I enter 1 into the calculatorWhen I add 1 to itThen the calculator should show 2 Acceptance Criteria (Plain Text)

33. Step Definitions Building Blocks Given I enter 1 into the calculatorWhen I add 1 to itThen the calculator should show 2 Acceptance Criteria (Plain Text) Given /^I enter (.+) into the calculator$/ do |number|@calculator = Calculator.new@calculator.enter(number.to_i)endWhen /^I add (.+) to it$/ do |number|@calculator.add(number.to_i)endWhen /^the calculator should show (.+)$/ do |number|@calculator.number.should == number.to_iend Step Definitions (Ruby)

34. Step Definitions Step Definitions Given /^I enter (.+) into the calculator$/ do |number|@calculator = Calculator.new@calculator.enter(number.to_i)endWhen /^I add (.+) to it$/ do |number|@calculator.add(number.to_i)endThen /^the calculator should show (.+)$/ do |number|@calculator.number.should == number.to_iend

35. Step Definitions Step Definitions Then /^the calculator should show (.+)$/ do |number|@calculator.number.should == number.to_iend

36. Step Definitions Step Definitions When I give a 45-minute long talk on Cucumber at 10:30am

37. Step Definitions Step Definitions When I give a 45-minute long talk on Cucumber at 10:30am

38. Step Definitions Step Definitions When I give a 45-minute long talk on Cucumber at 10:30am /I give a (+)-minute long talk on (.+) at (+):(+)(am|pm)/

39. Step Definitions Step Definitions When I give a 45-minute long talk on Cucumber at 10:30am /I give a (+)-minute long talk on (.+) at (+):(+)(am|pm)/

40. Step Definitions Step Definitions When I give a 45-minute long talk on Cucumber at 10:30am /I give a (+)-minute long talk on (.+) at (+):(+)(am|pm)/ do |duration_in_minutes, topic, start_hour, start_minute, am_pm|end

41. Multiple Given-When-Thens Scenario: Multiple Givens Given one thing Given another thing Given yet another thing When I open my eyes Then I see something Then I don't see something else Multiple Given-When-Thens

42. Or use And / But Scenario: Multiple Givens Given one thing And another thing And yet another thing When I open my eyes Then I see something But I don't see something else Or use And/But

43. Reuse Calling steps from within steps Given /^the user (.*) exists$/ do |name|#... end Given /^I log in as (.*)$/ do |name| #... end Given /^(.*) is logged in$/ do |name| Given "the user #{name} exists" Given "I log in as #{name}" end

44. Reuse Multiline step arguments - Tables Given the following people exist: | name | email | phone | | Farooq | farooq@email.com | 123 | | Mary | mary@email.com | 234 | | Bob | bob@email.org | 456 |

45. Reuse Multiline step arguments - Tables Given the following people exist: | name | email | phone | | Farooq | farooq@email.com | 123 | | Mary | mary@email.com | 234 | | Bob | bob@email.org | 456 | Given /the following people exist:/ do |people_table|people_table.hashes.each do |hash|# 1st: {'name' => ’Farooq', 'email' => ’farooq@email.com’, ... } # 2nd: {'name' => ’Mary', 'email' => ’mary@email.com', ... } # ...endend

46. Reuse Multiline step arguments - Strings Given a blog post named "Random" with Markdown body """ Some Title, Eh? ============== Here is the first paragraph of my blog post. Loremipsum dolor sit amet, consecteturadipiscingelit. """

47. Reuse Multiline step arguments - Strings Given a blog post named "Random" with Markdown body """ Some Title, Eh? ============== Here is the first paragraph of my blog post. Loremipsum dolor sit amet, consecteturadipiscingelit. """ Given /^a blog post named "([^quot;]*)" with Markdown body$/ do |title, markdown|Post.create!(:title=> title, :body => markdown)end

48. Tags Tags @billingFeature: Enter billing info@creditcardScenario: Credit card @paypal Scenario: PayPal

49. Hooks Hooks Before do# do something before first step of scenarioendAfter do# do something after each scenarioend

50. Tagged Hooks Tagged Hooks Before('@billing', '@calculations') do # This will only run before scenarios tagged # with @billing or @calculations. end

51. Global Hooks Global Hooks browser = Selenium::SeleniumDriver.new("localhost", 4444, "*chrome", "http://localhost", 15000) Given 'I am on the Google search page' do browser.open('http://www.google.com/’) end When /I search for "(.*)"/ do |query| browser.type('q', query) browser.click 'btnG’ browser.wait_for_page_to_load end Then /I should see a link to (.*)/ do |expected_url| browser.is_element_present("css=a[href='#{expected_url}']").should be_true end

52. Tags Backgrounds Feature: Multiple site support As a Mephisto site owner I want to host blogs for different people In order to make gigantic piles of money Background: Given a global administrator named “Greg” And a blog named “Greg’s anti-tax rants” And a customer named “Dr. Bill” And a blog named “Expensive Therapy” owned by “Dr. Bill” Scenario: Dr. Bill posts to his own blog Given I am logged in as Dr. Bill When I try to post to “Expensive Therapy” Then I should see “Your article was published.”

53. Global Hooks Step Argument Transforms # support file Transform /^user (+)$/ do |username| User.find_by_username(username) end # step definition file Then /^(user +) should be friends with (user +)$/ do |user,friend| user.shouldbe_friends_with(friend) end

54. Formatters cucumber -fjunit -–out <output_dir>

55. Formatters: Steps Feature: --formatter steps option - Steps Formatter In order to easily see which steps are already defined, specially when using 3rd party steps libraries, Cucumber should show the available steps in a user-friendly format Background: Given I am in steps_library Scenario: Printing steps When I run cucumber -f steps features Then it should pass with """ features/step_definitions/steps_lib1.rb /^I defined a first step$/ # features/step_definitions/steps_lib1.rb:1 /^I define a second step$/ # features/step_definitions/steps_lib1.rb:4 /^I should also have a third step$/ # features/step_definitions/steps_lib1.rb:7 features/step_definitions/steps_lib2.rb /^I defined a step 4$/ # features/step_definitions/steps_lib2.rb:1 /^I create a step 5$/ # features/step_definitions/steps_lib2.rb:4 /^I should be too tired for step 6$/ # features/step_definitions/steps_lib2.rb:7 6 step definition(s) in 2 source file(s). """

56. Formatters : JUnit Feature: JUnit output formatter In order for developers to create test reports with ant Cucumber should be able to output JUnit xml files Background: Given I am in junit And the tmp directory is empty @mri186 Scenario: one feature, one passing scenario, one failing scenario When I run cucumber --format junit --out tmp/ features/one_passing_one_failing.feature Then it should fail with """ """ And "examples/junit/tmp/TEST-one_passing_one_failing.xml" with junit duration "0.005" should contain """ <?xml version="1.0" encoding="UTF-8"?> <testsuite errors="0" failures="1" name="One passing scenario, one failing scenario" tests="2" time="0.005"> <testcaseclassname="One passing scenario, one failing scenario.Passing" name="Passing" time="0.005"> </testcase> <testcaseclassname="One passing scenario, one failing scenario.Failing" name="Failing" time="0.005"> <failure message="failed Failing" type="failed"> Scenario: Failing Given a failing scenario Message: (RuntimeError) features/one_passing_one_failing.feature:7:in `Given a failing scenario' </failure> </testcase> </testsuite> """ Scenario: pending steps are simply skipped When I run cucumber --format junit --out tmp/ features/pending.feature Then it should pass with """ """ And "examples/junit/tmp/TEST-pending.xml" with junit duration "0.009" should contain """ <?xml version="1.0" encoding="UTF-8"?> <testsuite errors="0" failures="0" name="Pending step" tests="0" time="0.009"> </testsuite> """ Scenario: pending step with strict option should fail When I run cucumber --format junit --out tmp/ features/pending.feature --strict Then it should fail with """ """ And "examples/junit/tmp/TEST-pending.xml" with junit duration "0.000160" should contain """ <?xml version="1.0" encoding="UTF-8"?> <testsuite errors="0" failures="1" name="Pending step" tests="1" time="0.000160"> <testcaseclassname="Pending step.Pending" name="Pending" time="0.000160"> <failure message="pending Pending" type="pending"> Scenario: Pending TODO (Cucumber::Pending) features/pending.feature:4:in `Given a pending step' </failure> </testcase> </testsuite> """ Scenario: run all features When I run cucumber --format junit --out tmp/ features Then it should fail with """ """ And "examples/junit/tmp/TEST-one_passing_one_failing.xml" should exist And "examples/junit/tmp/TEST-pending.xml" should exist Scenario: show correct error message if no --out is passed When I run cucumber --format junit features Then STDERR should not match """ can't convert .* into String TypeError """ And STDERR should match """ You must specify out DIR for the junit formatter """

57. Formatters : HTML Feature: HTML formatter In order to make it easy to read Cucumber results there should be a HTML formatter with an awesome CSS Scenario: Everything in examples/self_test When I run cucumber -q --format html --out tmp/a.html features Then "examples/self_test/tmp/a.html" should have the same contents as "features/html_formatter/a.html"