kbaum-cucumber 0.4.5.pre

data/examples/tickets/features/table_diffing.feature

@@ -0,0 +1,13 @@
+@intentional_failure
+Feature: Tables
+  Scenario: Extra row with table
+    Then the table should be different with table:
+      | a     | b    |
+      | one   | two  |
+      | three | four |
+
+  Scenario: Extra row and missing column with table
+    Then the table should be different with table:
+      | a     | e | b    |
+      | one   | Q | two  |
+      | three | R | four |

data/examples/tickets/features/tickets.feature

@@ -0,0 +1,28 @@
+Feature: Cucumber
+  In order to have a happy user base
+  As a Cucumber user
+  I don't want no stinkin bugs
+
+  Scenario: RSpec be_*
+    Given be_empty
+    
+  Scenario: Call step from step
+    Given nested step is called
+    Then nested step should be executed
+
+  Scenario: Call step from step using text table
+    Given nested step is called using text table
+    Then nested step should be executed
+    
+  Scenario: Reading a table
+    Given the following table
+      | born  | working |
+      | Oslo  | London  |
+    Then I should be working in London
+    And I should be born in Oslo
+    And I should see a multiline string like
+      """
+      A string
+      that spans
+      several lines
+      """

data/examples/watir/README.textile

@@ -0,0 +1,16 @@
+Here you'll find examples for Watir, FireWatir, SafariWatir and Celerity.
+All of these browser libraries have the same API, so the example code will
+work with all of them.
+
+Just run with:
+
+  rake cucumber
+  
+This will use Watir/IE if you're on Windows, and SafariWatir/Safari if you're on OS X.
+You can force the use of FireWatir/Firefox on any platform like this:
+
+  rake features FIREWATIR=true
+  
+And finally, you can use Celerity by running in JRuby:
+
+  jruby -S rake cucumber

data/examples/watir/Rakefile

@@ -0,0 +1,10 @@
+$:.unshift(File.dirname(__FILE__) + '/../../lib')
+require 'cucumber/rake/task'
+
+Cucumber::Rake::Task.new do |t|
+  t.cucumber_opts = %w{--format pretty}
+end
+
+Cucumber::Rake::Task.new(:cucumber_screenshot) do |t|
+  t.cucumber_opts = %w{--format html --out report.html}
+end

data/examples/watir/features/search.feature

@@ -0,0 +1,12 @@
+Feature: Search
+  In order to learn more
+  As an information seeker
+  I want to find more information
+
+  Scenario: Find what I'm looking for
+    Given I am on the Google search page
+    When I search for "cucumber github"
+    Then I should see
+      """
+      BDD that talks to domain experts first and code second
+      """

data/examples/watir/features/step_definitions/search_steps.rb

@@ -0,0 +1,26 @@
+# Full Watir API: http://wtr.rubyforge.org/rdoc/
+# Full RSpec API: http://rspec.rubyforge.org/
+
+Given 'I am on the Google search page' do
+  @browser.goto 'http://www.google.com/'
+end
+
+When /I search for "(.*)"/ do |query|
+  @browser.text_field(:name, 'q').set(query)
+  @browser.button(:name, 'btnG').click
+end
+
+Then /I should see/ do |text|
+  @browser.text.should =~ /#{text}/m
+end
+
+# To avoid step definitions that are tightly coupled to your user interface,
+# consider creating classes for your pages - such as this:
+# http://github.com/aslakhellesoy/cucumber/tree/v0.1.15/examples/watir/features/step_definitons/search_steps.rb
+#
+# You may keep the page classes along your steps, or even better, put them in separate files, e.g.
+# support/pages/google_search.rb
+#
+# This technique is called "Page Objects", and you can read more about it here:
+# http://github.com/marekj/watirloo/tree/master
+# We're not using this technique here, since we want to illustrate the basics only.

data/examples/watir/features/support/env.rb

@@ -0,0 +1,32 @@
+require 'spec/expectations'
+
+if ENV['FIREWATIR']
+  require 'firewatir'
+  Browser = FireWatir::Firefox
+else
+  case RUBY_PLATFORM
+  when /darwin/
+    require 'safariwatir'
+    Browser = Watir::Safari
+  when /win32|mingw/
+    require 'watir'
+    Browser = Watir::IE
+  when /java/
+    require 'celerity'
+    Browser = Celerity::Browser
+  else
+    raise "This platform is not supported (#{PLATFORM})"
+  end
+end
+
+# "before all"
+browser = Browser.new
+
+Before do
+  @browser = browser
+end
+
+# "after all"
+at_exit do
+  browser.close
+end

data/examples/watir/features/support/screenshots.rb

@@ -0,0 +1,44 @@
+# This is an example of how you can set up screenshots for your
+# browser testing. Just run cucumber with --format html --out report.html
+#
+# This examples currently only works on OS X, but adding support for other
+# platform should be easy - as long as there is a command line tool to take
+# a picture of the desktop.
+module Screenshots
+  def add_screenshot
+    id = "screenshot-#{Time.new.to_i}"
+    take_screenshot(id)
+    embed("#{id}.png", "image/png")
+  end
+
+  if Cucumber::OS_X
+    def take_screenshot(id)
+      `screencapture -t png #{id}.png`
+    end
+  else
+    # Other platforms...
+    def take_screenshot(id)
+      STDERR.puts "Sorry - no screenshots on your platform yet."
+    end
+  end
+end
+
+After do
+  add_screenshot
+end
+
+# Other variants
+#
+# Only take screenshot on failures
+#
+#   After do |scenario|
+#     add_screenshot if scenario.failed?
+#   end
+#
+# Only take screenshot for scenarios or features tagged @screenshot
+#
+#   After(@screenshot) do
+#     add_screenshot
+#   end
+
+World(Screenshots)

data/examples/webrat/features/search.feature

@@ -0,0 +1,12 @@
+Feature: Search
+  In order to learn more
+  As an information seeker
+  I want to find more information
+
+  Scenario: Find what I'm looking for
+    Given I am on the Kvasir search page
+    When I search for "cucumber github"
+    Then I should see
+      """
+      BDD that talks to domain experts first and code second
+      """

data/examples/webrat/features/step_definitions/kvasir_steps.rb

@@ -0,0 +1,14 @@
+# Google is too hard to script with Mechanize
+# Using a Norewgian search engine instead :-)
+Given /^I am on the Kvasir search page$/ do
+  visit('http://www.kvasir.no/')
+end
+
+When /^I search for "([^\"]*)"$/ do |query|
+  fill_in('q', :with => query)
+  click_button('sokeKnapp')
+end
+
+Then /^I should see$/ do |text|
+  response_body.should contain(text)
+end

data/examples/webrat/features/support/env.rb

@@ -0,0 +1,17 @@
+require 'webrat'
+require 'spec'
+
+Webrat.configure do |config|
+  config.mode = :mechanize
+end
+
+class WebratWorld
+  include Spec::Matchers
+  include Webrat::Methods
+  include Webrat::Matchers
+end
+
+World do
+  WebratWorld.new
+end
+ 

data/features/announce.feature

@@ -0,0 +1,122 @@
+Feature: Delayed announcement
+
+    Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+    """
+    Given /^I use announce with text "(.*)"$/ do |ann|
+        announce(ann)
+    end
+
+    Given /^I use multiple announces$/ do
+        announce("Multiple")
+        announce("Announce")
+    end
+
+    Given /^I use announcement (.+) in line (.+) (?:with result (.+))$/ do |ann, line, result|
+        announce("Last announcement") if line == "3"
+        announce("Line: #{line}: #{ann}")
+        fail if result =~ /fail/i
+    end
+
+    Given /^I use announce and step fails$/ do
+        announce("Announce with fail")
+        fail
+    end
+
+    Given /^this step works$/ do
+    end
+    """
+    And a file named "features/f.feature" with:
+    """
+    Scenario: S
+    Given I use announce with text "Ann"
+    And this step works
+
+    Scenario: S2
+    Given I use multiple announces
+    And this step works
+
+    Scenario Outline: S3
+    Given I use announcement <ann> in line <line>
+
+    Examples:
+    | line | ann |
+    | 1 | anno1 |
+    | 2 | anno2 |
+    | 3 | anno3 |
+
+    Scenario: S4
+    Given I use announce and step fails
+    And this step works
+
+    Scenario Outline: s5
+    Given I use announcement <ann> in line <line> with result <result>
+
+    Examples:
+    | line | ann | result |
+    | 1 | anno1 | fail |
+    | 2 | anno2 | pass |
+    """
+
+    Scenario: Delayed announcements feature
+    When I run cucumber --format pretty features/f.feature
+    Then the output should contain
+    """
+      Scenario: S                            # features/f.feature:1
+        Given I use announce with text "Ann" # features/step_definitions/steps.rb:1
+          Ann
+        And this step works                  # features/step_definitions/steps.rb:21
+
+      Scenario: S2                     # features/f.feature:5
+        Given I use multiple announces # features/step_definitions/steps.rb:5
+          Multiple
+          Announce
+        And this step works            # features/step_definitions/steps.rb:21
+
+      Scenario Outline: S3                            # features/f.feature:9
+        Given I use announcement <ann> in line <line> # features/f.feature:10
+
+        Examples: 
+          | line | ann   |
+          | 1    | anno1 |
+          | 2    | anno2 |
+          | 3    | anno3 |
+
+      Scenario: S4                          # features/f.feature:18
+        Given I use announce and step fails # features/step_definitions/steps.rb:16
+          Announce with fail
+           (RuntimeError)
+          ./features/step_definitions/steps.rb:18:in `/^I use announce and step fails$/'
+          features/f.feature:19:in `Given I use announce and step fails'
+        And this step works                 # features/step_definitions/steps.rb:21
+
+      Scenario Outline: s5                                                 # features/f.feature:22
+        Given I use announcement <ann> in line <line> with result <result> # features/step_definitions/steps.rb:10
+
+        Examples: 
+          | line | ann   | result |
+          | 1    | anno1 | fail   |  Line: 1: anno1
+           (RuntimeError)
+          ./features/step_definitions/steps.rb:13:in `/^I use announcement (.+) in line (.+) (?:with result (.+))$/'
+          features/f.feature:23:in `Given I use announcement <ann> in line <line> with result <result>'
+          | 2    | anno2 | pass   |  Line: 2: anno2
+"""
+
+    Scenario: Non-delayed announcements feature (progress formatter)
+      When I run cucumber --format progress features/f.feature
+      Then the output should contain
+    """
+Ann
+..
+Multiple
+
+Announce
+..-UUUUUU
+Announce with fail
+F--
+Line: 1: anno1
+FFF
+Line: 2: anno2
+...
+"""

data/features/background.feature

@@ -0,0 +1,308 @@
+Feature: backgrounds
+  In order to provide a context to my scenarios within a feature
+  As a feature editor
+  I want to write a background section in my features.
+
+  Scenario: run a specific scenario with a background
+    When I run cucumber -q features/background/passing_background.feature:9 --require features
+    Then it should pass with
+    """
+    Feature: Passing background sample
+    
+      Background: 
+        Given '10' cukes
+
+      Scenario: another passing background
+        Then I should have '10' cukes
+
+    1 scenario (1 passed)
+    2 steps (2 passed)
+    
+    """
+  
+  Scenario: run a feature with a background that passes
+    When I run cucumber -q features/background/passing_background.feature --require features
+    Then it should pass with
+    """
+    Feature: Passing background sample
+
+      Background: 
+        Given '10' cukes
+
+      Scenario: passing background
+        Then I should have '10' cukes
+
+      Scenario: another passing background
+        Then I should have '10' cukes
+
+    2 scenarios (2 passed)
+    4 steps (4 passed)
+    
+    """
+
+  Scenario: run a feature with scenario outlines that has a background that passes
+    When I run cucumber -q features/background/scenario_outline_passing_background.feature --require features
+    Then it should pass with
+    """
+    Feature: Passing background with scenario outlines sample
+
+      Background: 
+        Given '10' cukes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+      Scenario Outline: another passing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+    2 scenarios (2 passed)
+    4 steps (4 passed)
+
+    """
+
+  Scenario: run a feature with scenario outlines that has a background that passes
+    When I run cucumber -q features/background/background_tagged_before_on_outline.feature --require features
+    Then it should pass with
+    """
+    @background_tagged_before_on_outline
+    Feature: Background tagged Before on Outline
+
+      Background: 
+        Given passing without a table
+
+      Scenario Outline: passing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 888   |
+
+    1 scenario (1 passed)
+    2 steps (2 passed)
+
+    """
+
+  Scenario: run a feature with a background that fails
+    When I run cucumber -q features/background/failing_background.feature --require features
+    Then it should fail with
+    """
+    @after_file
+    Feature: Failing background sample
+
+      Background: 
+        Given failing without a table
+          FAIL (RuntimeError)
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+          features/background/failing_background.feature:5:in `Given failing without a table'
+        And '10' cukes
+
+      Scenario: failing background
+        Then I should have '10' cukes
+
+      Scenario: another failing background
+        Then I should have '10' cukes
+
+    Failing Scenarios:
+    cucumber features/background/failing_background.feature:8 # Scenario: failing background
+    
+    2 scenarios (1 failed, 1 skipped)
+    6 steps (1 failed, 5 skipped)
+
+    """
+    And "examples/self_test/tmp/after.txt" should exist
+
+  Scenario: run a feature with scenario outlines that has a background that fails
+    When I run cucumber -q features/background/scenario_outline_failing_background.feature --require features
+    Then it should fail with
+    """
+    Feature: Failing background with scenario outlines sample
+
+      Background: 
+        Given failing without a table
+          FAIL (RuntimeError)
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+          features/background/scenario_outline_failing_background.feature:4:in `Given failing without a table'
+
+      Scenario Outline: failing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+      Scenario Outline: another failing background
+        Then I should have '<count>' cukes
+
+        Examples: 
+          | count |
+          | 10    |
+
+    2 scenarios (1 failed, 1 skipped)
+    4 steps (1 failed, 3 skipped)
+
+    """
+
+  Scenario: run a feature with a background that is pending
+    When I run cucumber -q features/background/pending_background.feature --require features
+    Then it should pass with
+    """
+    Feature: Pending background sample
+
+      Background: 
+        Given pending
+
+      Scenario: pending background
+        Then I should have '10' cukes
+
+      Scenario: another pending background
+        Then I should have '10' cukes
+
+    2 scenarios (2 undefined)
+    4 steps (2 skipped, 2 undefined)
+
+    """
+
+  Scenario: background passes with first scenario but fails with second
+    When I run cucumber -q features/background/failing_background_after_success.feature --require features
+    Then it should fail with
+    """
+    Feature: Failing background after previously successful background sample
+
+      Background: 
+        Given passing without a table
+        And '10' global cukes
+
+      Scenario: passing background
+        Then I should have '10' global cukes
+
+      Scenario: failing background
+        And '10' global cukes
+          FAIL (RuntimeError)
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:37:in `/^'(.+)' global cukes$/'
+          features/background/failing_background_after_success.feature:5:in `And '10' global cukes'
+        Then I should have '10' global cukes
+
+    Failing Scenarios:
+    cucumber features/background/failing_background_after_success.feature:10 # Scenario: failing background
+
+    2 scenarios (1 failed, 1 passed)
+    6 steps (1 failed, 1 skipped, 4 passed)
+
+    """
+
+  Scenario: background with multline args
+  When I run cucumber -q features/background/multiline_args_background.feature --require features
+  Then it should pass with
+    """
+    Feature: Passing background with multiline args
+
+      Background: 
+        Given table
+          | a | b |
+          | c | d |
+        And multiline string
+          \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+          \"\"\"
+
+      Scenario: passing background
+        Then the table should be
+          | a | b |
+          | c | d |
+        Then the multiline string should be
+          \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+          \"\"\"
+
+      Scenario: another passing background
+        Then the table should be
+          | a | b |
+          | c | d |
+        Then the multiline string should be
+          \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+          \"\"\"
+
+    2 scenarios (2 passed)
+    8 steps (8 passed)
+    
+    """
+
+  Scenario: background with name
+    When I run cucumber -q features/background/background_with_name.feature --require features
+    Then it should pass with
+    """
+    Feature: background with name
+
+      Background: I'm a background and I'm ok
+        Given '10' cukes
+
+      Scenario: example
+        Then I should have '10' cukes
+
+    1 scenario (1 passed)
+    2 steps (2 passed)
+    
+    """
+
+  Scenario: https://rspec.lighthouseapp.com/projects/16211/tickets/329
+    Given a standard Cucumber project directory structure
+    And a file named "features/only_background_and_hooks.feature" with:
+      """
+      Feature: woo yeah
+
+        Background:
+          Given whatever
+
+      """
+    And a file named "features/only_background_and_hooks_steps.rb" with:
+      """
+      require 'spec/expectations'
+
+      Before do
+        $before = true
+      end
+
+      After do
+        $after = true
+      end
+
+      Given /^whatever$/ do
+        $before.should == true
+        $step = true
+      end
+
+      at_exit do
+        $before.should == true
+        $step.should == true
+        $after.should == true
+      end
+      """
+    When I run cucumber features/only_background_and_hooks.feature 
+    Then it should pass
+    And the output should be
+      """
+      Feature: woo yeah
+
+        Background:      # features/only_background_and_hooks.feature:3
+          Given whatever # features/only_background_and_hooks_steps.rb:11
+
+      0 scenarios
+      1 step (1 passed)
+      
+      """
+    And STDERR should be empty