cucumber 1.3.10 → 2.0.0

data/gem_tasks/yard.rake

@@ -1,40 +0,0 @@
-require 'yard'
-require 'yard/rake/yardoc_task'
-require File.expand_path(File.dirname(__FILE__) + '/../lib/cucumber/platform')
-
-DOC_DIR      = File.expand_path(File.dirname(__FILE__) + '/../doc')
-SITE_DIR     = File.expand_path(File.dirname(__FILE__) + '/../../cucumber.github.com')
-API_DIR      = File.join(SITE_DIR, 'api', 'cucumber', 'ruby', 'yardoc')
-TEMPLATE_DIR = File.expand_path(File.join(File.dirname(__FILE__), 'yard'))
-YARD::Templates::Engine.register_template_path(TEMPLATE_DIR)
-
-namespace :api do
-  YARD::Rake::YardocTask.new(:yard) do |yard|
-    yard.options = ["--out", DOC_DIR]
-  end
-
-  task :sync_with_git do
-    unless File.directory?(SITE_DIR)
-      raise "You need to git clone git@github.com:cucumber/cucumber.github.com.git #{SITE_DIR}"
-    end
-    Dir.chdir(SITE_DIR) do
-      sh 'git pull -u'
-    end
-  end
-
-  task :copy_to_website do
-    rm_rf API_DIR
-    cp_r DOC_DIR, API_DIR
-  end
-
-  task :release do
-    Dir.chdir(SITE_DIR) do
-      sh 'git add .'
-      sh "git commit -m 'Update API docs for Cucumber-Ruby v#{Cucumber::VERSION}'"
-      sh 'git push'
-    end
-  end
-
-  desc "Generate YARD docs for Cucumber's API"
-  task :doc => [:yard, :sync_with_git, :copy_to_website, :release]
-end

data/legacy_features/README.md

@@ -1,14 +0,0 @@
-# Please do not add to the tests in this folder
-
-This folder contains the acceptance tests that were written for Cucumber
-before [Aruba](https://github.com/cucumber/aruba) existed.
-
-These tests are currently run as part of the build, but should not be added to.
-
-New acceptance tests should be added in the `features` directory. If you find a test
-in here that you want to modify, please do the work to migrate it into the `features`
-directory.
-
-There is a ticket [#408](https://github.com/cucumber/cucumber/issues/408) to track 
-the effort to migrate all these tests into the `features` directory. We aim to have this
-completed for the release of Cucumber 2.0

data/legacy_features/announce.feature

@@ -1,152 +0,0 @@
-Feature: Delayed message
-
-  Background:
-    Given a standard Cucumber project directory structure
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^I use puts with text "(.*)"$/ do |ann| x=1
-        puts(ann)
-      end
-
-      Given /^I use multiple putss$/ do x=1
-        puts("Multiple")
-        puts("Announce","Me")
-      end
-
-      Given /^I use message (.+) in line (.+) (?:with result (.+))$/ do |ann, line, result| x=1
-        puts("Last message") if line == "3"
-        puts("Line: #{line}: #{ann}")
-        fail if result =~ /fail/i
-      end
-
-      Given /^I use puts and step fails$/ do x=1
-        puts("Announce with fail")
-        fail
-      end
-
-      Given /^this step works$/ do x=1
-      end
-
-      Given /^I puts the world$/ do x=1
-        puts(self)
-      end
-      """
-    And a file named "features/f.feature" with:
-      """
-      Feature: F
-
-        Scenario: S
-          Given I use puts with text "Ann"
-          And this step works
-
-        Scenario: S2
-          Given I use multiple putss
-          And this step works
-
-        Scenario Outline: S3
-          Given I use message <ann> in line <line>
-
-          Examples:
-            | line | ann |
-            | 1 | anno1 |
-            | 2 | anno2 |
-            | 3 | anno3 |
-
-        Scenario: S4
-          Given I use puts and step fails
-          And this step works
-
-        Scenario Outline: s5
-          Given I use message <ann> in line <line> with result <result>
-
-          Examples:
-            | line | ann | result |
-            | 1 | anno1 | fail |
-            | 2 | anno2 | pass |
-      """
-
-    And a file named "features/puts_world.feature" with:
-      """
-      Feature: puts_world
-        Scenario: puts_world
-          Given I puts the world
-      """
-
-    Scenario: Delayed messages feature
-      When I run cucumber --format pretty features/f.feature
-      Then STDERR should be empty
-      And the output should contain
-      """
-      Feature: F
-
-        Scenario: S                        # features/f.feature:3
-          Given I use puts 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:7
-          Given I use multiple putss # features/step_definitions/steps.rb:5
-            Multiple
-            Announce
-            Me
-          And this step works        # features/step_definitions/steps.rb:21
-
-        Scenario Outline: S3                       # features/f.feature:11
-          Given I use message <ann> in line <line> # features/f.feature:12
-
-          Examples: 
-            | line | ann   |
-            | 1    | anno1 |
-            | 2    | anno2 |
-            | 3    | anno3 |
-
-        Scenario: S4                      # features/f.feature:20
-          Given I use puts and step fails # features/step_definitions/steps.rb:16
-            Announce with fail
-             (RuntimeError)
-            ./features/step_definitions/steps.rb:18:in `/^I use puts and step fails$/'
-            features/f.feature:21:in `Given I use puts and step fails'
-          And this step works             # features/step_definitions/steps.rb:21
-
-        Scenario Outline: s5                                            # features/f.feature:24
-          Given I use message <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 message (.+) in line (.+) (?:with result (.+))$/'
-            features/f.feature:25:in `Given I use message <ann> in line <line> with result <result>'
-            | 2    | anno2 | pass   |  Line: 2: anno2
-      """
-
-    Scenario: Non-delayed messages feature (progress formatter)
-      When I run cucumber --format progress features/f.feature
-      Then the output should contain
-        """
-        Ann
-        ..
-        Multiple
-
-        Announce
-        Me
-        ..-UUUUUU
-        Announce with fail
-        F--
-        Line: 1: anno1
-        FFF
-        Line: 2: anno2
-        ...
-        """
-
-    @rspec2
-    Scenario: puts world
-      When I run cucumber --format progress features/puts_world.feature
-      Then the output should contain "RSpec::Matchers"
-      And the output should contain "Cucumber::RbSupport::RbWorld"
-
-    @rspec1
-    Scenario: puts world
-      When I run cucumber --format progress features/puts_world.feature
-      Then the output should contain "Spec::Matchers"
-      And the output should contain "Cucumber::RbSupport::RbWorld"

data/legacy_features/bug_371.feature

@@ -1,32 +0,0 @@
-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

@@ -1,16 +0,0 @@
-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

@@ -1,42 +0,0 @@
-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

@@ -1,22 +0,0 @@
-# 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

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