pezra-cucumber 0.3.94.1

data/features/junit_formatter.feature

@@ -0,0 +1,78 @@
+Feature: JUnit output formatter
+  In order for developers to create test reports with ant
+  Cucumber should be able to output JUnit xml files
+  
+  Background:
+    Given I am in junit
+    And the tmp directory is empty
+  
+  @mri186
+  Scenario: one feature, one passing scenario, one failing scenario
+    When I run cucumber --format junit --out tmp/ features/one_passing_one_failing.feature
+    Then it should fail with
+      """
+
+      """
+    And "examples/junit/tmp/TEST-one_passing_one_failing.xml" with junit duration "0.005" should contain
+      """
+      <?xml version="1.0" encoding="UTF-8"?>
+      <testsuite errors="0" failures="1" name="One passing scenario, one failing scenario" tests="2" time="0.005">
+      <testcase classname="One passing scenario, one failing scenario.Passing" name="Passing" time="0.005">
+      </testcase>
+      <testcase classname="One passing scenario, one failing scenario.Failing" name="Failing" time="0.005">
+        <failure message="failed Failing" type="failed">
+      Scenario: Failing
+
+      Given a failing scenario
+
+      Message:
+       (RuntimeError)
+      ./features/step_definitions/steps.rb:6:in `/a failing scenario/'
+      features/one_passing_one_failing.feature:7:in `Given a failing scenario'  </failure>
+      </testcase>
+      </testsuite>
+
+      """
+  
+  @mri186
+  Scenario: pending step
+    When I run cucumber --format junit --out tmp/ features/pending.feature
+    Then it should pass with
+      """
+      
+      """
+    And "examples/junit/tmp/TEST-pending.xml" with junit duration "0.009" should contain
+      """
+      <?xml version="1.0" encoding="UTF-8"?>
+      <testsuite errors="0" failures="1" name="Pending step" tests="1" time="0.009">
+      <testcase classname="Pending step.Pending" name="Pending" time="0.009">
+        <failure message="pending Pending" type="pending">
+      Scenario: Pending
+
+      TODO (Cucumber::Pending)
+      ./features/step_definitions/steps.rb:10:in `/a pending step/'
+      features/pending.feature:4:in `Given a pending step'  </failure>
+      </testcase>
+      </testsuite>
+      
+      """
+    
+  Scenario: run all features
+    When I run cucumber --format junit --out tmp/ features
+    Then it should fail with
+      """
+      
+      """
+    And "examples/junit/tmp/TEST-one_passing_one_failing.xml" should exist
+    And "examples/junit/tmp/TEST-pending.xml" should exist
+  
+  Scenario: show correct error message if no --out is passed
+    When I run cucumber --format junit features
+	  Then STDERR should not match 
+		  """
+can't convert .* into String \(TypeError\)
+		  """
+    And STDERR should match
+		  """
+You \*must\* specify \-\-out DIR for the junit formatter
+	    """

data/features/language_from_header.feature

@@ -0,0 +1,30 @@
+Feature: Language from header
+  In order to simplify command line and
+  settings in IDEs, Cucumber should pick
+  up parser language from a header.
+  
+  Scenario: LOLCAT
+    Given a standard Cucumber project directory structure
+    And a file named "features/lolcat.feature" with:
+      """
+      # language: en-lol
+      OH HAI: STUFFING
+        B4: HUNGRY
+        MISHUN: CUKES
+          DEN KTHXBAI
+      """
+    When I run cucumber -i features/lolcat.feature
+    Then it should pass with
+      """
+      # language: en-lol
+      OH HAI: STUFFING
+
+        B4: HUNGRY # features/lolcat.feature:3
+
+        MISHUN: CUKES # features/lolcat.feature:4
+          DEN KTHXBAI # features/lolcat.feature:5
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      """

data/features/multiline_names.feature

@@ -0,0 +1,43 @@
+Feature: Multiline description names
+  In order to accurately document feature elements
+  As a cucumberist
+  I want to have multiline names
+
+  Scenario: multiline scenario
+    When I run cucumber features/multiline_name.feature --no-snippets
+    Then it should pass with
+    """
+    Feature: multiline
+
+      Background: I'm a multiline name              # features/multiline_name.feature:3
+        which goes on and on and on for three lines
+        yawn
+        Given passing without a table               # features/step_definitions/sample_steps.rb:12
+
+      Scenario: I'm a multiline name                # features/multiline_name.feature:8
+        which goes on and on and on for three lines
+        yawn
+        Given passing without a table               # features/step_definitions/sample_steps.rb:12
+
+      Scenario Outline: I'm a multiline name        # features/multiline_name.feature:13
+        which goes on and on and on for three lines
+        yawn
+        Given <state> without a table               # features/step_definitions/sample_steps.rb:12
+
+        Examples: 
+          | state   |
+          | passing |
+
+      Scenario Outline: name          # features/multiline_name.feature:21
+        Given <state> without a table # features/step_definitions/sample_steps.rb:12
+
+        Examples: I'm a multiline name
+          which goes on and on and on for three lines
+          yawn
+          | state   |
+          | passing |
+
+    3 scenarios (3 passed)
+    6 steps (6 passed)
+
+    """

data/features/profiles.feature

@@ -0,0 +1,99 @@
+Feature: Profiles
+  In order to save time and prevent carpal tunnel syndrome
+  Cucumber users can save and reuse commonly used cucumber flags in a 'cucumber.yml' file.
+  These named arguments are called profiles and the yml file should be in the root of your project.
+  Any cucumber argument is valid in a profile.  To see all the available flags type 'cucumber --help'
+  For more information about profiles please see the wiki:
+  http://wiki.github.com/aslakhellesoy/cucumber/cucumberyml
+
+  Background: Basic App
+    Given a standard Cucumber project directory structure
+    And a file named "features/sample.feature" with:
+      """
+      Feature: Sample
+        Scenario: this is a test
+          Given I am just testing stuff
+      """
+    And a file named "features/support/env.rb"
+    And a file named "features/support/super_env.rb"
+    And the following profiles are defined:
+      """
+      default: features/sample.feature --require features/support/env.rb -v
+      super: features/sample.feature --require features/support/super_env.rb -v
+      """
+
+  Scenario: Explicitly defining a profile to run
+    When I run cucumber features/sample.feature --profile super
+    Then the output should contain
+      """
+      Using the super profile...
+      """
+    And exactly these files should be loaded: features/support/super_env.rb
+
+  Scenario: Defining multiple profiles to run
+    When I run cucumber features/sample.feature --profile default --profile super
+    Then the output should contain
+      """
+      Using the default and super profiles...
+      """
+    And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
+
+  Scenario: Arguments passed in but no profile specified
+    When I run cucumber -v
+    Then the default profile should be used
+    And exactly these files should be loaded: features/support/env.rb
+
+  Scenario: Trying to use a missing profile
+    When I run cucumber -p foo
+    Then STDERR should be
+      """
+      Could not find profile: 'foo'
+
+      Defined profiles in cucumber.yml:
+        * default
+        * super
+
+      """
+
+  Scenario Outline: Disabling the default profile
+    When I run cucumber -v features/ <Flag>
+    Then the output should contain
+      """
+      Disabling profiles...
+      """
+    And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
+
+    Examples:
+    |   Flag          |
+    | -P              |
+    | --no-profile    |
+
+
+  Scenario: Overriding the profile's features to run
+    Given a file named "features/another.feature" with:
+      """
+      Feature: Just this one should be ran
+      """
+      When I run cucumber -p default features/another.feature
+      Then exactly these features should be ran: features/another.feature
+
+  Scenario: Overriding the profile's formatter
+    You will most likely want to define a formatter in your default formatter.
+    However, you often want to run your features with a different formatter
+    yet still use the other the other arguments in the profile. Cucumber will
+    allow you to do this by giving precedence to the formatter specified on the
+    command line and override the one in the profile.
+
+    Given the following profiles are defined:
+      """
+      default: features/sample.feature --require features/support/env.rb -v --format profile
+      """
+    When I run cucumber features --format pretty
+    And the output should contain
+      """
+      Feature: Sample
+      """
+
+
+
+

data/features/rake_task.feature

@@ -0,0 +1,178 @@
+Feature: Rake task
+  In order to ease the development process
+  As a developer and CI server administrator
+  Cucumber features should be executable via Rake
+
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/missing_step_definitions.feature" with:
+      """
+      Feature: Sample
+
+        Scenario: Wanted
+          Given I want to run this
+
+        Scenario: Unwanted
+          Given I don't want this ran
+      """
+
+
+  Scenario: rake task with a defined profile
+    Given the following profile is defined:
+      """
+      foo: --quiet --no-color features/missing_step_definitions.feature:3
+      """
+    And a file named "Rakefile" with:
+      """
+      $LOAD_PATH.unshift(CUCUMBER_LIB)
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new(:features) do |t|
+        t.profile = "foo"
+      end
+      """
+    When I run rake features
+    Then it should pass
+    And the output should contain
+      """
+      Feature: Sample
+
+        Scenario: Wanted
+          Given I want to run this
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+
+  Scenario: rake task with a defined profile and cucumber_opts
+    Given the following profile is defined:
+      """
+      bar: ['features/missing_step_definitions.feature:3']
+      """
+    And a file named "Rakefile" with:
+      """
+      $LOAD_PATH.unshift(CUCUMBER_LIB)
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new(:features) do |t|
+        t.profile = "bar"
+        t.cucumber_opts = %w{--quiet --no-color}
+      end
+      """
+    When I run rake features
+    Then it should pass
+    And the output should contain
+      """
+      Feature: Sample
+
+        Scenario: Wanted
+          Given I want to run this
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+
+  Scenario: rake task with a defined profile and feature list
+    Given a file named "features/the_one_i_want_to_run.feature" with:
+      """
+      Feature: Desired
+
+        Scenario: Something
+          Given this is missing
+      """
+    Given the following profile is defined:
+      """
+      baz: ['--quiet', '--no-color']
+      """
+    And a file named "Rakefile" with:
+      """
+      $LOAD_PATH.unshift(CUCUMBER_LIB)
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new(:features) do |t|
+        t.profile = "baz"
+        t.feature_list = ['features/the_one_i_want_to_run.feature']
+      end
+      """
+    When I run rake features
+    Then it should pass
+    And the output should contain
+      """
+      Feature: Desired
+
+        Scenario: Something
+          Given this is missing
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+
+  Scenario: deprecation warnings
+    Given a file named "Rakefile" with:
+      """
+      $LOAD_PATH.unshift(CUCUMBER_LIB)
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new(:features) do |t|
+        t.feature_list = ['features/missing_step_definitions.feature']
+      end
+      """
+    When I run rake features
+    Then it should pass
+    And STDERR should match
+      """
+      Cucumber::Rake::Task#feature_list is deprecated and will be removed in 0.4.0.  Please use profiles for complex settings: http://wiki.github.com/aslakhellesoy/cucumber/using-rake#profiles
+      """
+
+  Scenario: respect requires
+    Given a file named "features/support/env.rb"
+    And a file named "features/support/dont_require_me.rb"
+    And the following profile is defined:
+      """
+      no_bomb: features/missing_step_definitions.feature:3 --require features/support/env.rb --verbose
+      """
+    And a file named "Rakefile" with:
+      """
+      $LOAD_PATH.unshift(CUCUMBER_LIB)
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new(:features) do |t|
+        t.profile = "no_bomb"
+        t.cucumber_opts = %w{--quiet --no-color}
+      end
+      """
+
+    When I run rake features
+    Then it should pass
+    And the output should not contain
+      """
+        * features/support/dont_require_me.rb
+      """
+
+  Scenario: feature files with spaces
+    Given a file named "features/spaces are nasty.feature" with:
+       """
+       Feature: The futures green
+
+         Scenario: Orange
+           Given this is missing
+       """
+    And a file named "Rakefile" with:
+       """
+       $LOAD_PATH.unshift(CUCUMBER_LIB)
+       require 'cucumber/rake/task'
+
+       Cucumber::Rake::Task.new(:features) do |t|
+         t.cucumber_opts = %w{--quiet --no-color}
+       end
+       """
+    When I run rake features
+    Then it should pass
+    And the output should contain
+       """
+       Feature: The futures green
+
+         Scenario: Orange
+           Given this is missing
+
+       """

data/features/report_called_undefined_steps.feature

@@ -0,0 +1,35 @@
+Feature: Cucumber command line
+  In order to find out what step definitions need to be implemented
+  Developers should always see what step definition is missing
+
+  @mri186
+  Scenario: Get info at arbitrary levels of nesting
+    When I run cucumber features/call_undefined_step_from_step_def.feature
+    Then it should pass with
+      """
+      Feature: Calling undefined step
+
+        Scenario: Call directly                                # features/call_undefined_step_from_step_def.feature:3
+          Given a step definition that calls an undefined step # features/step_definitions/sample_steps.rb:19
+            Undefined step: "this does not exist" (Cucumber::Undefined)
+            ./features/step_definitions/sample_steps.rb:20:in `/^a step definition that calls an undefined step$/'
+            features/call_undefined_step_from_step_def.feature:4:in `Given a step definition that calls an undefined step'
+
+        Scenario: Call via another                                         # features/call_undefined_step_from_step_def.feature:6
+          Given call step "a step definition that calls an undefined step" # features/step_definitions/sample_steps.rb:23
+            Undefined step: "this does not exist" (Cucumber::Undefined)
+            ./features/step_definitions/sample_steps.rb:20:in `/^a step definition that calls an undefined step$/'
+            features/call_undefined_step_from_step_def.feature:7:in `Given call step "a step definition that calls an undefined step"'
+
+      2 scenarios (2 undefined)
+      2 steps (2 undefined)
+
+      You can implement step definitions for undefined steps with these snippets:
+
+      Given /^this does not exist$/ do
+        pending
+      end
+
+
+      """
+