cucumber 1.3.20 → 2.0.0.beta.1

data/features/assertions.feature

@@ -1,73 +0,0 @@
-Feature: Assertions
-  In order to get started quickly
-  As a new Cucumber user
-  I want to use a familiar assertion library
-
-  Background:
-    Given a file named "features/assert.feature" with:
-       """
-       Feature: Assert
-         Scenario: Passing
-           Then it should pass
-       """
-
-    Given a file named "without_rspec.rb" with:
-    """
-    require 'rubygems' if RUBY_VERSION <= '1.8.7'
-    require 'rspec/expectations'
-
-    module RSpec
-      remove_const :Matchers rescue nil
-      remove_const :Expectations rescue nil
-    end
-
-    module Spec
-      remove_const :Expectations rescue nil
-    end
-    """
-
-  @spawn
-  Scenario: Test::Unit
-    Given a file named "features/step_definitions/assert_steps.rb" with:
-      """
-      require 'test/unit/assertions'
-      World(::Test::Unit::Assertions)
-
-      Then /^it should pass$/ do
-        assert(2 + 2 == 4)
-      end
-      """
-    When I run `cucumber`
-    Then it should pass with exactly:
-      """
-      Feature: Assert
-
-        Scenario: Passing     # features/assert.feature:2
-          Then it should pass # features/step_definitions/assert_steps.rb:4
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-      0m0.012s
-
-      """
-
-  Scenario: RSpec
-    Given a file named "features/step_definitions/assert_steps.rb" with:
-      """
-      Then /^it should pass$/ do
-        (2 + 2).should == 4
-      end
-      """
-    When I run `cucumber`
-    Then it should pass with exactly:
-      """
-      Feature: Assert
-
-        Scenario: Passing     # features/assert.feature:2
-          Then it should pass # features/step_definitions/assert_steps.rb:1
-
-      1 scenario (1 passed)
-      1 step (1 passed)
-      0m0.012s
-
-      """

data/features/autoformat_profile_output.feature

@@ -1,23 +0,0 @@
-Feature: Autoformat profile output
-
-  Background:
-    Given a file named "features/autoformat_output_has_profile_info.feature" with:
-      """
-      Feature:
-
-        Scenario: Passing
-          Given passing
-      """
-
-  Scenario: when using a profile the output should include 'Using the default profile...'
-    And a file named "cucumber.yml" with:
-    """
-      default: -r features
-    """
-    When I run `cucumber --profile default --autoformat tmp`
-    Then it should pass
-    And the output should contain:
-    """
-    Using the default profile...
-    """
-

data/features/before_hook.feature

@@ -1,43 +0,0 @@
-Feature: Before Hook
-
-  Scenario: Examine names of elements
-    Given a file named "features/foo.feature" with:
-      """
-      Feature: Feature name
-
-        Scenario: Scenario name
-          Given a step
-
-        Scenario Outline: Scenario Outline name
-          Given a <placeholder>
-
-          Examples: Examples Table name
-            | <placeholder> |
-            | step          |
-      """
-    And a file named "features/support/hook.rb" with:
-      """
-      names = []
-      Before do |scenario|
-        unless scenario.respond_to?(:scenario_outline)
-          names << scenario.feature.name.split("\n").first
-          names << scenario.name.split("\n").first
-        else
-          names << scenario.scenario_outline.feature.name.split("\n").first
-          names << scenario.scenario_outline.name.split("\n").first
-        end
-        if(names.size == 4)
-          raise "NAMES:\n" + names.join("\n") + "\n"
-        end
-      end
-      """
-    When I run `cucumber`
-    Then the output should contain:
-      """
-            NAMES:
-            Feature name
-            Scenario name
-            Feature name
-            Scenario Outline name
-      """
-

data/features/bootstrap.feature

@@ -1,26 +0,0 @@
-Feature: Bootstrapping a new project
-  In order to have the best chances of getting up and running with cucumber
-  As a new cucumber user
-  I want cucumber to give helpful error messages in basic situations
-
- @spawn
- Scenario: running cucumber against a non-existing feature file
-  Given a directory without standard Cucumber project directory structure
-    When I run `cucumber`
-    Then it should fail with:
-      """
-      Please create a features directory to get started. (Errno::ENOENT)
-      """
-
- @spawn
- Scenario: does not load ruby files in root if features directory is missing
-  Given a directory without standard Cucumber project directory structure
-  And a file named "should_not_load.rb" with:
-    """
-    puts 'this will not be shown'
-    """
-  When I run `cucumber`
-  Then it should fail with:
-    """
-    Please create a features directory to get started. (Errno::ENOENT)
-    """

data/features/drb_server_integration.feature

@@ -1,63 +0,0 @@
-@drb @wip-jruby @spawn
-Feature: DRb Server Integration
-  To prevent waiting for Rails and other large Ruby applications to load their environments
-  for each feature run Cucumber ships with a DRb client that can speak to a server which
-  loads up the environment only once.
-
-  This regression test highlights bug related to DRb server arguments processing, for more
-  details see https://github.com/cucumber/cucumber/issues/117
-
-  Background: App with Spork support
-    Spork is a gem that has a DRb server and the scenarios below illustrate how to use it.
-    However, any DRb server that adheres to the protocol that the client expects would work.
-
-    Given a directory without standard Cucumber project directory structure
-    And a file named "features/support/env.rb" with:
-      """
-      require 'rubygems'
-      require 'spork'
-
-      Spork.prefork do
-        puts "I'm loading all the heavy stuff..."
-      end
-
-      Spork.each_run do
-        puts "I'm loading the stuff just for this run..."
-      end
-      """
-    And a file named "config/cucumber.yml" with:
-      """
-      <%
-      std_opts = "--format #{ENV['CUCUMBER_FORMAT'] || 'pretty'} --strict --tags ~@wip"
-      %>
-      default: --drb <%= std_opts %> features
-      """
-    And a file named "features/sample.feature" with:
-      """
-      # language: en
-      Feature: Sample
-        Scenario: this is a test
-          Given I am just testing stuff
-      """
-    And a file named "features/step_definitions/all_your_steps_are_belong_to_us.rb" with:
-    """
-    Given /^I am just testing stuff$/ do
-      # no-op
-    end
-    """
-
-  Scenario: Single feature passing with '-r features' option
-    Given I am running spork in the background
-    When I run `cucumber features/sample.feature -r features --tags ~@wip`
-    And it should pass with:
-    """
-    1 step (1 passed)
-    """
-
-  Scenario: Single feature passing without '-r features' option
-    Given I am running spork in the background
-    When I run `cucumber features/sample.feature --tags ~@wip`
-    And it should pass with:
-    """
-    1 step (1 passed)
-    """

data/features/execute_with_tag_filter.feature

@@ -1,63 +0,0 @@
-Feature: Tag logic
-  In order to conveniently run subsets of features
-  As a Cuker
-  I want to select features using logical AND/OR of tags
-
-  Background:
-    Given a file named "features/tagulicious.feature" with:
-      """
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-          Given passing
-
-        @one
-        Scenario: Another Example
-          Given passing
-
-        @three
-        Scenario: Yet another Example
-          Given passing
-
-        @ignore
-        Scenario: And yet another Example
-      """
-
-  Scenario: ANDing tags
-    When I run `cucumber -q -t @one -t @three features/tagulicious.feature`
-    Then it should pass with:
-      """
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-          Given passing
-
-      1 scenario (1 undefined)
-      1 step (1 undefined)
-
-      """
-
-  Scenario: ORing tags
-    When I run `cucumber -q -t @one,@three features/tagulicious.feature`
-    Then it should pass with:
-      """
-      Feature: Sample
-
-        @one @three
-        Scenario: Example
-          Given passing
-
-        @one
-        Scenario: Another Example
-          Given passing
-
-        @three
-        Scenario: Yet another Example
-          Given passing
-
-      3 scenarios (3 undefined)
-      3 steps (3 undefined)
-
-      """

data/features/parsing.feature

@@ -1,18 +0,0 @@
-Feature: Scenario Outlines
-
-  Scenario: Scenario Outline requires Example Section
-    Given a file named "features/f.feature" with:
-      """
-      Feature:
-        Scenario Outline:
-          Given I have <opening balance> cucumbers
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /^I have (\d+) cucumbers$/ do; end
-      """
-    When I run `cucumber features/f.feature`
-    Then it should fail with:
-      """
-      Missing Example Section for Scenario Outline at features/f.feature:2 (Cucumber::Ast::ScenarioOutline::MissingExamples)
-      """

data/features/rerun_formatter.feature

@@ -1,99 +0,0 @@
-Feature: Rerun formatter
-  For details see https://github.com/cucumber/cucumber/issues/57
-
-  Background:
-    Given a file named "features/one_passing_one_failing.feature" with:
-      """
-      Feature: One passing example, one failing example
-
-        Scenario Outline:
-          Given a <certain> step
-        
-        Examples:
-          |certain|
-          |passing|
-          |failing|
-
-      """
-    Given a file named "features/passing_outline.feature" with:
-      """
-      Feature: One passing example
-
-        Scenario Outline:
-          Given a <certain> step
-        
-        Examples:
-          |certain|
-          |passing|
-
-      """
-    And a file named "features/failing_background.feature" with:
-      """
-      Feature: Failing background sample
-
-        Background:
-          Given a failing step
-
-        Scenario: failing background
-          Then a passing step
-
-        Scenario: another failing background
-          Then a passing step
-      """
-    And a file named "features/failing_background_outline.feature" with:
-      """
-      Feature: Failing background sample with scenario outline
-
-        Background:
-          Given a failing step
-
-        Scenario Outline:
-          Then a <certain> step
-
-        Examples:
-          |certain|
-          |passing|
-          |passing|
-      """
-    And a file named "features/step_definitions/steps.rb" with:
-      """
-      Given /a passing step/ do
-        #does nothing
-      end
-
-      Given /a failing step/ do
-        fail
-      end
-      """
-
-  Scenario: Handle examples with the rerun formatter
-    When I run `cucumber features/one_passing_one_failing.feature -r features -f rerun`
-    Then it should fail with:
-    """
-    features/one_passing_one_failing.feature:9
-    """
-
-  Scenario: Handle examples using expand with the rerun formatter
-    When I run `cucumber features/one_passing_one_failing.feature --expand -r features -f rerun`
-    Then it should fail with:
-    """
-    features/one_passing_one_failing.feature:9
-    """
-
-  Scenario: Handle scenario outline with passing example
-    When I run `cucumber features/passing_outline.feature -r features -f rerun`
-    Then it should pass
-
-  Scenario: Failing background
-    When I run `cucumber features/failing_background.feature -r features -f rerun`
-    Then it should fail with:
-    """
-    features/failing_background.feature:6:9
-    """
-
-  Scenario: Failing background with scenario outline
-    When I run `cucumber features/failing_background_outline.feature -r features -f rerun`
-    Then it should fail with:
-    """
-    features/failing_background_outline.feature:11:12
-    """

data/features/run_specific_scenarios.feature

@@ -1,47 +0,0 @@
-Feature: Run specific scenarios
-
-  You can choose to run a specific scenario using the file:line format
-
-  Background:
-    Given a file named "features/step_definitions/steps.rb" with:
-      """
-      Given(/pass/) {}
-      Given(/fail/) { raise "Failed" }
-      """
-
-  Scenario: Two scenarios, run just one of them
-    Given a file named "features/test.feature" with:
-      """
-      Feature: 
-        Scenario:
-          Given this is undefined
-
-        Scenario: Hit
-          Given this passes
-      """
-    When I run `cucumber features/test.feature:5 -f progress`
-    Then it should pass with:
-      """
-      1 scenario (1 passed)
-      """
-
-  Scenario: Single example from a scenario outline
-    Given a file named "features/test.feature" with:
-      """
-      Feature:
-        Scenario Outline:
-          Given this <something>
-
-          Examples:
-            | something    |
-            | is undefined |
-            | fails        |
-
-        Scenario: Miss
-          Given this passes
-      """
-    When I run `cucumber features/test.feature:8 -f progress`
-    Then it should fail with:
-      """
-      1 scenario (1 failed)
-      """