pezra-cucumber 0.3.94.1

data/examples/tickets/features/step_definitons/tickets_steps.rb

@@ -0,0 +1,81 @@
+require 'spec/expectations'
+
+Given "be_empty" do
+  [1,2].should_not be_empty
+end
+
+Given "nested step is called" do
+  Given "I like mushroom", Cucumber::Ast::Table.new([
+    %w{sponge bob},
+    %w{is cool}
+  ])
+end
+
+Given 'nested step is called using text table' do
+  Given "I like mushroom", table(%{
+    | sponge | bob  |
+    | is     | cool |
+  })
+
+  # Alternative syntax (file and line will be reported on parse error)
+  # Given "I like mushroom", table(<<-EOT, __FILE__, __LINE__)
+  #   | sponge | bob  |
+  #   | is     | cool
+  # EOT
+end
+
+Given "I like $what" do |what, table|
+  @magic = what
+  @tool  = table.raw[0][0]
+end
+
+Then "nested step should be executed" do
+  @magic.should == 'mushroom'
+  @tool.should == 'sponge'
+end
+
+Given /^the following table$/ do |table|
+  @table = table
+end
+
+Then /^I should be (\w+) in (\w+)$/ do |key, value|
+  hash = @table.hashes[0]
+  hash[key].should == value
+end
+
+Then /^I should see a multiline string like$/ do |s|
+  s.should == %{A string
+that spans
+several lines}
+end
+
+Given /^the following users exist in the system$/ do |table|
+  table.hashes[0][:role_assignments].should == 'HUMAN RESOURCE'
+end
+
+Given /^I have a pending step$/ do
+  pending
+end
+
+When /^I run this feature with the progress format$/ do
+  pending
+end
+
+Then /^I should get a no method error for 'backtrace_line'$/ do
+  pending
+end
+
+Then /the table should be different with table:/ do |expected|
+  expected.diff!(table(%{
+    | b     | c    | a     | d |
+    | KASHA | AIIT | BOOYA | X |
+    | four  | five | three | Y |
+  }), :coldiff => true)
+end
+
+Then /the table should be different with array:/ do |expected|
+  expected.diff!([
+    {'a' => 'BOOYA', 'b' => 'KASHA'},
+    {'a' => 'three', 'b' => 'four'},
+  ])
+end

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 features
+  
+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 features

data/examples/watir/Rakefile

@@ -0,0 +1,6 @@
+$:.unshift(File.dirname(__FILE__) + '/../../lib')
+require 'cucumber/rake/task'
+
+Cucumber::Rake::Task.new do |t|
+  t.cucumber_opts = %w{--format pretty}
+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_definitons/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/features/after_block_exceptions.feature

@@ -0,0 +1,102 @@
+Feature: After Block Exceptions
+  In order to use custom assertions at the end of each scenario
+  As a developer
+  I want exceptions raised in After blocks to be handled gracefully and reported by the formatters
+  
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step does something naughty$/ do
+        @naughty = true
+      end
+
+      Given /^this step works$/ do        
+      end
+      """
+    And a file named "features/support/env.rb" with:
+      """
+      class NaughtyScenarioException < Exception; end
+      After do
+        if @naughty
+          raise NaughtyScenarioException.new("This scenario has been very very naughty")
+        end
+      end
+      """
+
+  @mri186
+  Scenario: Handle Exception in standard scenario step and carry on
+    Given a file named "features/naughty_step_in_scenario.feature" with:
+      """
+      Feature: Sample
+
+        Scenario: Naughty Step
+          Given this step does something naughty
+
+        Scenario: Success
+          Given this step works
+      """
+    When I run cucumber features
+    Then it should fail with 
+      """
+      Feature: Sample
+      
+        Scenario: Naughty Step                   # features/naughty_step_in_scenario.feature:3
+          Given this step does something naughty # features/step_definitions/steps.rb:1
+            This scenario has been very very naughty (NaughtyScenarioException)
+            ./features/support/env.rb:4:in `After'
+
+        Scenario: Success       # features/naughty_step_in_scenario.feature:6
+          Given this step works # features/step_definitions/steps.rb:5
+      
+      Failing Scenarios:
+      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
+      
+      2 scenarios (1 failed, 1 passed)
+      2 steps (2 passed)
+      
+      """
+
+  @mri186
+  Scenario: Handle Exception in scenario outline table row and carry on
+    Given a file named "features/naughty_step_in_scenario_outline.feature" with:
+      """
+      Feature: Sample
+
+        Scenario Outline: Naughty Step
+          Given this step <Might Work>
+          
+          Examples:
+          | Might Work             |
+          | works                  |
+          | does something naughty |
+          | works                  |
+
+        Scenario: Success
+          Given this step works
+          
+      """
+    When I run cucumber features
+    Then it should fail with 
+      """
+      Feature: Sample
+      
+        Scenario Outline: Naughty Step # features/naughty_step_in_scenario_outline.feature:3
+          Given this step <Might Work> # features/step_definitions/steps.rb:5
+      
+          Examples: 
+            | Might Work             |
+            | works                  |
+            | does something naughty |
+            This scenario has been very very naughty (NaughtyScenarioException)
+            ./features/support/env.rb:4:in `After'
+            | works                  |
+      
+        Scenario: Success       # features/naughty_step_in_scenario_outline.feature:12
+          Given this step works # features/step_definitions/steps.rb:5
+      
+      4 scenarios (1 failed, 3 passed)
+      4 steps (4 passed)
+      
+      """
+  

data/features/after_step_block_exceptions.feature

@@ -0,0 +1,104 @@
+Feature: AfterStep Block Exceptions
+  In order to use custom assertions at the end of each step
+  As a developer
+  I want exceptions raised in AfterStep blocks to be handled gracefully and reported by the formatters
+  
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step does something naughty$/ do
+        @naughty = true
+      end
+
+      Given /^this step works$/ do        
+      end
+      """
+    And a file named "features/support/env.rb" with:
+      """
+      class NaughtyStepException < Exception; end
+      AfterStep do
+        if @naughty
+          raise NaughtyStepException.new("This step has been very very naughty")
+        end
+      end
+      """
+
+  @mri186
+  Scenario: Handle Exception in standard scenario step and carry on
+    Given a file named "features/naughty_step_in_scenario.feature" with:
+      """
+      Feature: Sample
+
+        Scenario: Naughty Step
+          Given this step does something naughty
+
+        Scenario: Success
+          Given this step works
+      """
+    When I run cucumber features
+    Then it should fail with 
+      """
+      Feature: Sample
+      
+        Scenario: Naughty Step                   # features/naughty_step_in_scenario.feature:3
+          Given this step does something naughty # features/step_definitions/steps.rb:1
+            This step has been very very naughty (NaughtyStepException)
+            ./features/support/env.rb:4:in `AfterStep'
+            features/naughty_step_in_scenario.feature:4:in `Given this step does something naughty'
+
+        Scenario: Success       # features/naughty_step_in_scenario.feature:6
+          Given this step works # features/step_definitions/steps.rb:5
+      
+      Failing Scenarios:
+      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
+      
+      2 scenarios (1 failed, 1 passed)
+      2 steps (1 failed, 1 passed)
+      
+      """
+
+  @mri186
+  Scenario: Handle Exception in scenario outline table row and carry on
+    Given a file named "features/naughty_step_in_scenario_outline.feature" with:
+      """
+      Feature: Sample
+
+        Scenario Outline: Naughty Step
+          Given this step <Might Work>
+
+          Examples:
+          | Might Work             |
+          | works                  |
+          | does something naughty |
+          | works                  |
+
+        Scenario: Success
+          Given this step works
+
+      """
+    When I run cucumber features
+    Then it should fail with 
+      """
+      Feature: Sample
+
+        Scenario Outline: Naughty Step # features/naughty_step_in_scenario_outline.feature:3
+          Given this step <Might Work> # features/step_definitions/steps.rb:5
+
+          Examples: 
+            | Might Work             |
+            | works                  |
+            | does something naughty |
+            This step has been very very naughty (NaughtyStepException)
+            ./features/support/env.rb:4:in `AfterStep'
+            features/naughty_step_in_scenario_outline.feature:4:in `Given this step <Might Work>'
+            | works                  |
+
+        Scenario: Success       # features/naughty_step_in_scenario_outline.feature:12
+          Given this step works # features/step_definitions/steps.rb:5
+
+      4 scenarios (1 failed, 3 passed)
+      4 steps (1 failed, 3 passed)
+
+      """
+

data/features/background.feature

@@ -0,0 +1,311 @@
+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)
+
+    """
+
+  @mri186
+  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
+
+  @mri186
+  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)
+
+    """
+
+  @mri186
+  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