casecumber 1.0.2.1

data/legacy_features/api/list_step_defs_as_json.feature

@@ -0,0 +1,50 @@
+Feature: List step defs as json
+  In order to build tools on top of Cucumber
+  As a tool developer
+  I want to be able to query a features directory for all the step definitions it contains
+  
+  Background: 
+    Given a standard Cucumber project directory structure
+  
+  Scenario: Two Ruby step definitions, in the same file
+    Given a file named "features/step_definitions/foo_steps.rb" with:
+      """
+      Given(/foo/i) {}
+      Given(/b.r/xm) {}
+      """
+    When I run the following Ruby code:
+      """
+      require 'cucumber'
+      puts Cucumber::StepDefinitions.new.to_json
+      
+      """
+    Then it should pass
+    And the output should contain the following JSON:
+      """
+      [
+        {"source": "foo", "flags": "i"},
+        {"source": "b.r", "flags": "mx"}
+      ]
+      """
+
+  Scenario: Non-default directory structure
+    Given a file named "my_weird/place/foo_steps.rb" with:
+      """
+      Given(/foo/) {}
+      Given(/b.r/x) {}
+      """
+    When I run the following Ruby code:
+      """
+      require 'cucumber'
+      puts Cucumber::StepDefinitions.new(:autoload_code_paths => ['my_weird']).to_json
+      
+      """
+    Then it should pass
+    And the output should contain the following JSON:
+      """
+      [
+        {"source": "foo", "flags": ""},
+        {"source": "b.r", "flags": "x"}
+      ]
+      
+      """

data/legacy_features/api/run_cli_main_with_existing_runtime.feature

@@ -0,0 +1,34 @@
+Feature: Run Cli::Main with existing Runtime
+
+  This is the API that Spork uses. It creates an existing runtime then
+  calls load_programming_language('rb') on it to load the RbDsl.
+  When the process forks, Spork them passes the runtime to Cli::Main to 
+  run it.
+
+    Background: 
+      Given a standard Cucumber project directory structure
+
+    Scenario: Run a single feature
+      Given a file named "features/step_definitions/success.rb" with:
+        """
+        Given(/pass/) {}
+        """
+      Given a file named "features/success.feature" with:
+        """
+        Feature: 
+          Scenario: 
+            Given I pass
+        """
+      When I run the following Ruby code:
+        """
+        require 'cucumber'
+        runtime = Cucumber::Runtime.new
+        runtime.load_programming_language('rb')
+        Cucumber::Cli::Main.new([]).execute!(runtime)
+        
+        """
+      Then it should pass
+      And the output should contain:
+        """
+        Given I pass
+        """

data/legacy_features/around_hooks.feature

@@ -0,0 +1,232 @@
+Feature: Around hooks
+  In order to support transactional scenarios for database libraries
+  that provide only a block syntax for transactions, Cucumber should
+  permit definition of Around hooks.
+
+  Scenario: A single Around hook
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the hook is called$/ do
+        $hook_called.should == true
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hook_called = true
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        Scenario: using hook
+          Then the hook is called
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        Scenario: using hook      # features/f.feature:2
+          Then the hook is called # features/step_definitions/steps.rb:1
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Multiple Around hooks
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the hooks are called in the correct order$/ do
+        $hooks_called.should == ['A', 'B', 'C']
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'A'
+        block.call
+      end
+
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'B'
+        block.call
+      end
+
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'C'
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        Scenario: using multiple hooks
+          Then the hooks are called in the correct order
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        Scenario: using multiple hooks                   # features/f.feature:2
+          Then the hooks are called in the correct order # features/step_definitions/steps.rb:1
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Mixing Around, Before, and After hooks
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the Around hook is called around Before and After hooks$/ do
+        $hooks_called.should == ['Around', 'Before']
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'Around'
+        block.call
+        $hooks_called << 'Around'
+        $hooks_called.should == ['Around', 'Before', 'After', 'Around']
+      end
+
+      Before do |scenario|
+        $hooks_called ||= []
+        $hooks_called << 'Before'
+      end
+
+      After do |scenario|
+        $hooks_called ||= []
+        $hooks_called << 'After'
+        $hooks_called.should == ['Around', 'Before', 'After']
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        Scenario: Mixing Around, Before, and After hooks
+          Then the Around hook is called around Before and After hooks
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        Scenario: Mixing Around, Before, and After hooks               # features/f.feature:2
+          Then the Around hook is called around Before and After hooks # features/step_definitions/steps.rb:1
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Around hooks with tags
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the Around hooks with matching tags are called$/ do
+        $hooks_called.should == ['one', 'one or two']
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around('@one') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'one'
+        block.call
+      end
+
+      Around('@one,@two') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'one or two'
+        block.call
+      end
+
+      Around('@one', '@two') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'one and two'
+        block.call
+      end
+
+      Around('@two') do |scenario, block|
+        $hooks_called ||= []
+        $hooks_called << 'two'
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks
+        @one
+        Scenario: Around hooks with tags
+          Then the Around hooks with matching tags are called
+      """
+    When I run cucumber -q -t @one features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks
+
+        @one
+        Scenario: Around hooks with tags
+          Then the Around hooks with matching tags are called
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Around hooks with scenario outlines
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Then /^the hook is called$/ do
+        $hook_called.should == true
+      end
+      """
+    And a file named "features/support/hooks.rb" with:
+      """
+      Around do |scenario, block|
+        $hook_called = true
+        block.call
+      end
+      """
+    And a file named "features/f.feature" with:
+      """
+      Feature: Around hooks with scenario outlines
+        Scenario Outline: using hook
+          Then the hook is called
+
+          Examples:
+            | Number |
+            | one    |
+            | two    |
+      """
+    When I run cucumber features/f.feature
+    Then it should pass with
+      """
+      Feature: Around hooks with scenario outlines
+
+        Scenario Outline: using hook # features/f.feature:2
+          Then the hook is called    # features/step_definitions/steps.rb:1
+
+          Examples: 
+            | Number |
+            | one    |
+            | two    |
+
+      2 scenarios (2 passed)
+      2 steps (2 passed)
+
+      """

data/legacy_features/bug_371.feature

@@ -0,0 +1,32 @@
+Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/371
+  Scenario: Before runs once
+    Given a standard Cucumber project directory structure
+    And a file named "features/f.feature" with:
+      """
+      Feature: F
+        Scenario: S
+          Given G
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Before do
+        puts "B"
+      end
+      Given /G/ do
+        puts "G"
+      end
+      """
+    When I run cucumber -q --format pretty --format progress --out progress.txt features/f.feature
+    Then it should pass with
+      """
+      Feature: F
+
+        Scenario: S
+          Given G
+            B
+            G
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """

data/legacy_features/bug_464.feature

@@ -0,0 +1,16 @@
+Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/464
+  Scenario: Limiting with tags which do not exist in the features
+    Given a standard Cucumber project directory structure
+    And a file named "features/f.feature" with:
+      """
+      Feature: Test
+      In order to test
+      As a tester
+      I want to test
+
+        @tag
+        Scenario: Testing
+          Given I'm a test
+      """
+    When I run cucumber -q features/f.feature --tag @i_dont_exist
+    Then it should pass

data/legacy_features/bug_475.feature

@@ -0,0 +1,42 @@
+Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/475
+  Scenario: error on pystring in scenario outline with pretty formatter
+    Given a standard Cucumber project directory structure
+    And a file named "features/f.feature" with:
+      """
+      Feature: F
+        Scenario Outline: S
+          Given a multiline string:
+             \"\"\"
+             hello <who>
+             \"\"\"
+        Examples:
+          | who   |
+          | aslak |
+          | david |
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /a multiline string:/ do |s| s.should =~ /hello (\w+)/
+      end
+      """
+    When I run cucumber features/f.feature
+    Then STDERR should be empty
+    And it should pass with
+      """
+      Feature: F
+
+        Scenario Outline: S         # features/f.feature:2
+          Given a multiline string: # features/step_definitions/steps.rb:1
+            \"\"\"
+            hello <who>
+            \"\"\"
+
+          Examples: 
+            | who   |
+            | aslak |
+            | david |
+
+      2 scenarios (2 passed)
+      2 steps (2 passed)
+      
+      """

data/legacy_features/bug_585_tab_indentation.feature

@@ -0,0 +1,22 @@
+# Make sure tab indentation is preserved in this feature!
+Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/585
+	Scenario: Tab indentation should work
+    	Given a standard Cucumber project directory structure
+    	And a file named "features/f.feature" with:
+		"""
+		Feature: developer creates a skeleton Ruby application
+			Scenario: create a new application
+				Given a tab indented pystring:
+				\"\"\"
+				I'm tab
+				 and space indented
+				\"\"\"
+			And a file named "features/step_definitions/steps.rb" with:
+				\"\"\"
+				Given /a tab indented pystring:/ do |s| s.should == "I'm tab\n and space indented"
+				end
+				\"\"\"
+		"""
+		When I run cucumber features/f.feature
+		Then STDERR should be empty
+		And it should pass

data/legacy_features/bug_600.feature

@@ -0,0 +1,73 @@
+Feature: http://rspec.lighthouseapp.com/projects/16211/tickets/600-inconsistent-order-of-execution-background-and-before-in-070beta2
+
+  Scenario: Background executed twice when scenario follows scenario outline
+    Given a standard Cucumber project directory structure
+    And a file named "features/t.feature" with:
+      """
+      Feature: test
+        Background: 
+          Given I am in the background
+
+        Scenario Outline: test 1
+          Given I am a step
+
+          Examples:
+            | a |
+            | 1 |
+
+        Scenario: test 2
+      """
+    And a file named "features/step_definitions/t_steps.rb" with:
+      """
+      Given "I am in the background" do
+        puts "Within background"
+      end
+
+      Given "I am a step" do
+        # no-op
+      end
+      """
+    And a file named "features/support/env.rb" with:
+      """
+      module TestWorld
+        def before_scenario
+          puts "Before scenario"
+        end
+
+        def after_scenario
+          puts "After scenario"
+        end
+      end
+
+      World(TestWorld)
+
+      Before do
+        before_scenario
+      end
+
+      After do
+        after_scenario
+      end
+      """
+    When I run cucumber -f progress features/t.feature
+    Then it should pass with
+      """
+
+      Before scenario
+      
+      Within background
+      .--
+      After scenario
+      
+      Before scenario
+      
+      Within background
+      .
+      After scenario
+      
+      
+      2 scenarios (2 passed)
+      3 steps (3 passed)
+
+      """
+