cucumber 0.8.5 → 0.8.6

data/examples/i18n/ar/features/step_definitons/calculator_steps.rb

@@ -15,7 +15,7 @@ Given "كتابة $n في الآلة الحاسبة" do |n|
   @calc.push n.to_i
 end
 
-When /يتم الضغط على (\w+)/ do |op|
+When /يتم الضغط على (.+)/ do |op|
   @result = @calc.send op
 end
 

data/examples/i18n/he/features/step_definitons/calculator_steps.rb

@@ -15,7 +15,7 @@ Given /שהזנתי (\d+) למחשבון/ do |n|
   @calc.push n.to_i
 end
 
-When /אני לוחץ על (\w+)/ do |op|
+When /אני לוחץ על (.+)/ do |op|
   @result = @calc.send op
 end
 

data/examples/i18n/ro/features/step_definitons/calculator_steps.rb

@@ -4,21 +4,18 @@ require 'cucumber/formatter/unicode'
 $:.unshift(File.dirname(__FILE__) + '/../../lib') 
 require 'calculator'
 
-Before do
+Datfiind /un calculator/ do
   @calc = Calculator.new
 end
 
-After do
-end
-
-Given /introduc (\d+)/ do |n|
+Cand /introduc (\d+)/ do |n|
   @calc.push n.to_i
 end
 
-When 'apas suma' do
+Cand 'apăs tasta Egal' do
   @result = @calc.add
 end
 
-Then /rezultatul trebuie sa fie (\d*)/ do |result|
+Atunci /ecranul trebuie să afişeze (\d*)/ do |result|
   @result.should == result.to_i
 end

data/examples/i18n/ru/features/division.feature

@@ -1,5 +1,5 @@
 # language: ru
-Фича: Деление чисел
+Функция: Деление чисел
   Поскольку деление сложный процесс и люди часто допускают ошибки
   Нужно дать им возможность делить на калькуляторе
 
@@ -9,7 +9,7 @@
     Если я нажимаю "/"
     То результатом должно быть число <частное>
 
-  Значения:
+  Примеры:
     | делимое | делитель | частное |
     | 100     | 2        | 50      |
     | 28      | 7        | 4       |

data/examples/i18n/tr/features/step_definitons/hesap_makinesi_adimlari.rb

@@ -11,14 +11,14 @@ end
 After do
 end
 
-Given /hesap makinesine (\d+) girdim/ do |n|
+Diyelimki /hesap makinesine (\d+) girdim/ do |n|
   @calc.push n.to_i
 end
 
-When /(\w+) tuşuna basarsam/ do |op|
+Eğerki /(.*) tuşuna basarsam/ do |op|
   @result = @calc.send op
 end
 
-Then /ekrandaki sonuç (.*) olmalı/ do |result|
+Ozaman /ekrandaki sonuç (.*) olmalı/ do |result|
   @result.should == result.to_f
 end

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

@@ -1,10 +1,7 @@
-# See http://wiki.github.com/aslakhellesoy/cucumber/sinatra
+# See http://wiki.github.com/cucumber/cucumber/sinatra
 # for more details about Sinatra with Cucumber
 
-app_file = File.join(File.dirname(__FILE__), *%w[.. .. app.rb])
-require app_file
-# Force the application name because polyglot breaks the auto-detection logic.
-Sinatra::Application.app_file = app_file
+require File.dirname(__FILE__) + '/../../app'
 
 begin require 'rspec/expectations'; rescue LoadError; require 'spec/expectations'; end
 require 'rack/test'

data/examples/v8/features/fibonacci.feature

@@ -17,7 +17,7 @@ Feature: Fibonacci
       | 9   | [1, 1, 2, 3, 5, 8]                     |
       | 100 | [1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] |
 
-  Scenario: Single series tested via a PyString
+  Scenario: Single series tested via a DocString
     When I ask Javascript to calculate fibonacci up to 2 with formatting
     Then it should give me:
     """

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

@@ -16,7 +16,7 @@ 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
+# http://github.com/cucumber/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

data/features/background.feature

@@ -1,12 +1,195 @@
-Feature: backgrounds
+Feature: Background
   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.
 
+  Background:
+    Given a file named "features/passing_background.feature" 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
+      """
+    And a file named "features/scenario_outline_passing_background.feature" 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  |
+      """
+    And a file named "features/background_tagged_before_on_outline.feature" 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   |
+      """
+    And a file named "features/failing_background.feature" with:
+      """
+      Feature: Failing background sample
+
+        Background:
+          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
+      """
+    And a file named "features/scenario_outline_failing_background.feature" with:
+      """
+      Feature: Failing background with scenario outlines sample
+
+        Background:
+          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  |
+      """
+    And a file named "features/pending_background.feature" 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
+      """
+    And a file named "features/failing_background_after_success.feature" 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
+          Then I should have '10' global cukes
+      """
+    And a file named "features/multiline_args_background.feature" 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
+            \"\"\"
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      def flunker
+        raise "FAIL"
+      end
+
+      Given /^'(.+)' cukes$/ do |cukes| x=1
+        raise "We already have #{@cukes} cukes!" if @cukes
+        @cukes = cukes
+      end
+
+      Given(/^passing without a table$/) do
+      end
+
+      Given /^failing without a table$/ do x=1
+        flunker
+      end
+
+      Given /^'(.+)' global cukes$/ do |cukes| x=1
+        $scenario_runs ||= 0
+        flunker if $scenario_runs >= 1
+        $cukes = cukes
+        $scenario_runs += 1
+      end
+
+      Then /^I should have '(.+)' global cukes$/ do |cukes| x=1
+        $cukes.should == cukes
+      end
+
+      Then /^I should have '(.+)' cukes$/ do |cukes| x=1
+        @cukes.should == cukes
+      end
+
+      Before('@background_tagged_before_on_outline') do
+        @cukes = '888'
+      end
+
+      After('@background_tagged_before_on_outline') do
+        @cukes.should == '888'
+      end
+      """
+
   Scenario: run a specific scenario with a background
-    When I run cucumber -q features/background/passing_background.feature:9 --require features
-    Then STDERR should be empty
-    Then it should pass with
+    When I run `cucumber -q features/passing_background.feature:9`
+    Then it should pass with exactly:
     """
     Feature: Passing background sample
     
@@ -18,12 +201,13 @@ Feature: backgrounds
 
     1 scenario (1 passed)
     2 steps (2 passed)
-    
+    0m0.012s
+
     """
   
   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
+    When I run `cucumber -q features/passing_background.feature`
+    Then it should pass with exactly:
     """
     Feature: Passing background sample
 
@@ -38,12 +222,13 @@ Feature: backgrounds
 
     2 scenarios (2 passed)
     4 steps (4 passed)
-    
+    0m0.012s
+
     """
 
   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
+    When I run `cucumber -q features/scenario_outline_passing_background.feature`
+    Then it should pass with exactly:
     """
     Feature: Passing background with scenario outlines sample
 
@@ -66,12 +251,13 @@ Feature: backgrounds
 
     2 scenarios (2 passed)
     4 steps (4 passed)
+    0m0.012s
 
     """
 
   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
+    When I run `cucumber -q features/background_tagged_before_on_outline.feature`
+    Then it should pass with exactly:
     """
     @background_tagged_before_on_outline
     Feature: Background tagged Before on Outline
@@ -88,22 +274,22 @@ Feature: backgrounds
 
     1 scenario (1 passed)
     2 steps (2 passed)
+    0m0.012s
 
     """
 
   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
+    When I run `cucumber -q features/failing_background.feature`
+    Then it should fail with exactly:
     """
-    @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'
+          ./features/step_definitions/steps.rb:2:in `flunker'
+          ./features/step_definitions/steps.rb:14:in `/^failing without a table$/'
+          features/failing_background.feature:4:in `Given failing without a table'
         And '10' cukes
 
       Scenario: failing background
@@ -113,26 +299,26 @@ Feature: backgrounds
         Then I should have '10' cukes
 
     Failing Scenarios:
-    cucumber features/background/failing_background.feature:8 # Scenario: failing background
+    cucumber features/failing_background.feature:7 # Scenario: failing background
     
     2 scenarios (1 failed, 1 skipped)
     6 steps (1 failed, 5 skipped)
-
+    0m0.012s
+    
     """
-    And "fixtures/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
+    When I run `cucumber -q features/scenario_outline_failing_background.feature`
+    Then it should fail with exactly:
     """
     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'
+          ./features/step_definitions/steps.rb:2:in `flunker'
+          ./features/step_definitions/steps.rb:14:in `/^failing without a table$/'
+          features/scenario_outline_failing_background.feature:4:in `Given failing without a table'
 
       Scenario Outline: failing background
         Then I should have '<count>' cukes
@@ -149,16 +335,17 @@ Feature: backgrounds
           | 10    |
 
     Failing Scenarios:
-    cucumber features/background/scenario_outline_failing_background.feature:6 # Scenario: failing background
+    cucumber features/scenario_outline_failing_background.feature:6 # Scenario: failing background
 
     2 scenarios (1 failed, 1 skipped)
     4 steps (1 failed, 3 skipped)
-
+    0m0.012s
+    
     """
 
   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
+    When I run `cucumber -q features/pending_background.feature`
+    Then it should pass with exactly:
     """
     Feature: Pending background sample
 
@@ -173,12 +360,13 @@ Feature: backgrounds
 
     2 scenarios (2 undefined)
     4 steps (2 skipped, 2 undefined)
-
+    0m0.012s
+    
     """
 
   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
+    When I run `cucumber -q features/failing_background_after_success.feature`
+    Then it should fail with exactly:
     """
     Feature: Failing background after previously successful background sample
 
@@ -192,84 +380,86 @@ Feature: backgrounds
       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'
+          ./features/step_definitions/steps.rb:2:in `flunker'
+          ./features/step_definitions/steps.rb:19:in `/^'(.+)' global cukes$/'
+          features/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
+    cucumber features/failing_background_after_success.feature:10 # Scenario: failing background
 
     2 scenarios (1 failed, 1 passed)
     6 steps (1 failed, 1 skipped, 4 passed)
-
+    0m0.012s
+    
     """
 
   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
+    Given a file named "features/step_definitions/multiline_steps.rb" with:
+      """
+      Given /^table$/ do |table| x=1
+        @table = table
+      end
 
-      Background: 
-        Given table
-          | a | b |
-          | c | d |
-        And multiline string
-          \"\"\"
+      Given /^multiline string$/ do |string| x=1
+        @multiline = string
+      end
+
+      Then /^the table should be$/ do |table| x=1
+        @table.raw.should == table.raw
+      end
+
+      Then /^the multiline string should be$/ do |string| x=1
+        @multiline.should == string
+      end
+      """
+    When I run `cucumber -q features/multiline_args_background.feature`
+    Then it should pass with exactly:
+      """
+      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
-          \"\"\"
+            \"\"\"
+
+        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
-          \"\"\"
+            \"\"\"
+
+        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)
+      2 scenarios (2 passed)
+      8 steps (8 passed)
+      0m0.012s
     
-    """
-
-  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:
+    Given a file named "features/only_background_and_hooks.feature" with:
       """
       Feature: woo yeah
 
-        Background:
+        Background: Whatever
           Given whatever
 
       """
@@ -293,17 +483,16 @@ Feature: backgrounds
         $after.should == true
       end
       """
-    When I run cucumber features/only_background_and_hooks.feature 
-    Then it should pass
-    And the output should be
+    When I run `cucumber features/only_background_and_hooks.feature`
+    Then it should pass with exactly:
       """
       Feature: woo yeah
 
-        Background:      # features/only_background_and_hooks.feature:3
-          Given whatever # features/only_background_and_hooks_steps.rb:11
+        Background: Whatever # features/only_background_and_hooks.feature:3
+          Given whatever     # features/only_background_and_hooks_steps.rb:11
 
       0 scenarios
       1 step (1 passed)
-      
+      0m0.012s
+
       """
-    And STDERR should be empty