mobiusloop 0.1.2

data/features/docs/gherkin/using_star_notation.feature

@@ -0,0 +1,37 @@
+Feature: Using star notation instead of Given/When/Then
+
+  Cucumber supports the star notation when writing features: instead of
+  using Given/When/Then, you can simply use a star rather like you would
+  use a bullet point.
+
+  When you run the feature for the first time, you still get a nice
+  message showing you the code snippet you need to use to implement the
+  step.
+
+  Scenario: Use some *
+    Given a file named "features/f.feature" with:
+      """
+      Feature: Star-notation feature
+        Scenario: S
+          * I have some cukes
+      """
+    When I run `cucumber features/f.feature`
+    Then the stderr should not contain anything
+    And it should pass with:
+      """
+      Feature: Star-notation feature
+
+        Scenario: S           # features/f.feature:2
+          * I have some cukes # features/f.feature:3
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+    And it should pass with:
+      """
+      You can implement step definitions for undefined steps with these snippets:
+
+      Given(/^I have some cukes$/) do
+        pending # Write code here that turns the phrase above into concrete actions
+      end
+      """

data/features/docs/iso-8859-1.feature

@@ -0,0 +1,6 @@
+# language: no
+# encoding: iso-8859-1
+Egenskap: Alle bruker ikke UTF-8
+  Scenario: Dette b�r g� bra
+    N�r jeg drikker en "�l"
+    S� skal de andre si "sk�l"

data/features/docs/post_configuration_hook.feature

@@ -0,0 +1,49 @@
+Feature: Post Configuration Hook [#423]
+
+  In order to extend Cucumber
+  As a developer
+  I want to manipulate the Cucumber configuration after it has been created
+
+  # Fails on Travis under JRuby
+  @spawn
+  @wip-jruby
+  Scenario: Using options directly gets a deprecation warning
+    Given a file named "features/support/env.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.options[:blah]
+      end
+      """
+    When I run `cucumber features`
+    Then the stderr should contain:
+      """
+      Deprecated
+      """
+
+  Scenario: Changing the output format
+    Given a file named "features/support/env.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.formats << ['html', config.out_stream]
+      end
+      """
+    When I run `cucumber features`
+    Then the stderr should not contain anything
+    And the output should contain:
+      """
+      html
+      """
+
+  Scenario: feature directories read from configuration
+    Given a file named "features/support/env.rb" with:
+      """
+      AfterConfiguration do |config|
+        config.out_stream << "AfterConfiguration hook read feature directories: #{config.feature_dirs.join(', ')}"
+      end
+      """
+    When I run `cucumber features`
+    Then the stderr should not contain anything
+    And the output should contain:
+      """
+      AfterConfiguration hook read feature directories: features
+      """

data/features/docs/profiles.feature

@@ -0,0 +1,120 @@
+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/cucumber/cucumber/cucumber.yml
+
+  Background: Basic App
+    Given a file named "features/sample.feature" with:
+      """
+      Feature: Sample
+        Scenario: this is a test
+          Given this step raises an error
+      """
+    And an empty file named "features/support/env.rb"
+    And an empty 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: Explicitly defining a profile defined in an ERB formatted file
+    Given the following profiles are defined:
+      """
+      <% requires = "--require features/support/super_env.rb" %>
+      super: <%= "features/sample.feature #{requires} -v" %>
+      """
+    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 the stderr should contain:
+      """
+      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 run
+      """
+    When I run `cucumber -p default features/another.feature`
+    Then exactly these features should be run: 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`
+    Then the output should contain:
+      """
+      Feature: Sample
+      """
+
+  Scenario Outline: Showing profiles when listing failing scenarios
+    Given the standard step definitions
+    When I run `cucumber -q -p super -p default -f <format> features/sample.feature --require features/step_definitions/steps.rb`
+    Then it should fail with:
+       """
+       cucumber -p super features/sample.feature:2
+       """
+
+    Examples:
+      | format   |
+      | pretty   |
+      | progress |

data/features/docs/rake_task.feature

@@ -0,0 +1,141 @@
+@spawn
+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:
+    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:
+      """
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new do |t|
+        t.profile = "foo"
+      end
+      """
+    When I run `rake cucumber`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        Scenario: Wanted
+          Given I want to run this
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+
+  Scenario: rake task without a profile
+    Given a file named "Rakefile" with:
+      """
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new do |t|
+        t.cucumber_opts = %w{--quiet --no-color}
+      end
+      """
+    When I run `rake cucumber`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        Scenario: Wanted
+          Given I want to run this
+
+        Scenario: Unwanted
+          Given I don't want this ran
+
+      2 scenarios (2 undefined)
+      2 steps (2 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:
+      """
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new do |t|
+        t.profile = "bar"
+        t.cucumber_opts = %w{--quiet --no-color}
+      end
+      """
+    When I run `rake cucumber`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        Scenario: Wanted
+          Given I want to run this
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+
+  Scenario: respect requires
+    Given an empty file named "features/support/env.rb"
+    And an empty 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:
+      """
+      require 'cucumber/rake/task'
+
+      Cucumber::Rake::Task.new do |t|
+        t.profile = "no_bomb"
+        t.cucumber_opts = %w{--quiet --no-color}
+      end
+      """
+    When I run `rake cucumber`
+    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:
+       """
+       require 'cucumber/rake/task'
+
+       Cucumber::Rake::Task.new do |t|
+         t.cucumber_opts = %w{--quiet --no-color}
+       end
+       """
+    When I run `rake cucumber`
+    Then it should pass with:
+       """
+       Feature: The futures green
+
+         Scenario: Orange
+           Given this is missing
+
+       """

data/features/docs/raketask.feature

@@ -0,0 +1,44 @@
+@spawn
+Feature: Raketask
+
+  In order to use cucumber's rake task
+  As a Cuker
+  I do not want to see rake's backtraces when it fails
+  Also I want to get zero exit status code on failures
+  And non-zero exit status code when it pases
+
+  Background:
+    Given the standard step definitions
+    Given a file named "features/passing_and_failing.feature" with:
+      """
+      Feature: Sample
+
+        Scenario: Passing
+          Given this step passes
+
+        Scenario: Failing
+          Given this step raises an error
+      """
+    Given a file named "Rakefile" with:
+      """
+        require 'cucumber/rake/task'
+
+        SAMPLE_FEATURE_FILE = 'features/passing_and_failing.feature'
+
+        Cucumber::Rake::Task.new(:pass) do |t|
+          t.cucumber_opts = "#{SAMPLE_FEATURE_FILE}:3"
+        end
+
+        Cucumber::Rake::Task.new(:fail) do |t|
+          t.cucumber_opts = "#{SAMPLE_FEATURE_FILE}:6"
+        end
+      """
+
+  Scenario: Passing feature
+    When I run `bundle exec rake pass`
+    Then the exit status should be 0
+
+  Scenario: Failing feature
+    When I run `bundle exec rake fail`
+    Then the exit status should be 1
+    But the output should not contain "rake aborted!"

data/features/docs/work_in_progress.feature

@@ -0,0 +1,154 @@
+@spawn
+Feature: Cucumber --work-in-progress switch
+  In order to ensure that feature scenarios do not pass until they are expected to
+  Developers should be able to run cucumber in a mode that
+            - will fail if any scenario passes completely
+            - will not fail otherwise
+
+  Background: A passing and a pending feature
+    Given the standard step definitions
+    And a file named "features/wip.feature" with:
+      """
+      Feature: WIP
+        @failing
+        Scenario: Failing
+          Given this step raises an error
+
+        @undefined
+        Scenario: Undefined
+          Given this step is undefined
+
+        @pending
+        Scenario: Pending
+          Given this step is pending
+
+        @passing
+        Scenario: Passing
+          Given this step passes
+      """
+    And a file named "features/passing_outline.feature" with:
+      """
+      Feature: Not WIP
+        Scenario Outline: Passing
+          Given this step <what>
+
+          Examples:
+            | what   |
+            | passes |
+      """
+
+  Scenario: Pass with Failing Scenarios
+    When I run `cucumber -q -w -t @failing features/wip.feature`
+    Then the stderr should not contain anything
+    Then it should pass with:
+      """
+      Feature: WIP
+
+        @failing
+        Scenario: Failing
+          Given this step raises an error
+            error (RuntimeError)
+            ./features/step_definitions/steps.rb:2:in `/^this step raises an error$/'
+            features/wip.feature:4:in `Given this step raises an error'
+
+      Failing Scenarios:
+      cucumber features/wip.feature:3
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+      """
+    And the output should contain:
+      """
+      The --wip switch was used, so the failures were expected. All is good.
+
+      """
+
+  Scenario: Pass with Undefined Scenarios
+    When I run `cucumber -q -w -t @undefined features/wip.feature`
+    Then it should pass with:
+      """
+      Feature: WIP
+
+        @undefined
+        Scenario: Undefined
+          Given this step is undefined
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+      """
+    And the output should contain:
+      """
+      The --wip switch was used, so the failures were expected. All is good.
+
+      """
+
+  Scenario: Pass with Undefined Scenarios
+    When I run `cucumber -q -w -t @pending features/wip.feature`
+    Then it should pass with:
+      """
+      Feature: WIP
+
+        @pending
+        Scenario: Pending
+          Given this step is pending
+            TODO (Cucumber::Pending)
+            ./features/step_definitions/steps.rb:3:in `/^this step is pending$/'
+            features/wip.feature:12:in `Given this step is pending'
+
+      1 scenario (1 pending)
+      1 step (1 pending)
+      """
+    And the output should contain:
+      """
+      The --wip switch was used, so the failures were expected. All is good.
+
+      """
+
+  Scenario: Fail with Passing Scenarios
+    When I run `cucumber -q -w -t @passing features/wip.feature`
+    Then it should fail with:
+      """
+      Feature: WIP
+
+        @passing
+        Scenario: Passing
+          Given this step passes
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+      """
+    And the output should contain:
+      """
+      The --wip switch was used, so I didn't expect anything to pass. These scenarios passed:
+      (::) passed scenarios (::)
+
+      features/wip.feature:15:in `Scenario: Passing'
+
+
+      """
+
+  Scenario: Fail with Passing Scenario Outline
+    When I run `cucumber -q -w features/passing_outline.feature`
+    Then it should fail with:
+      """
+      Feature: Not WIP
+
+        Scenario Outline: Passing
+          Given this step <what>
+
+          Examples: 
+            | what   |
+            | passes |
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+      """
+    And the output should contain:
+      """
+      The --wip switch was used, so I didn't expect anything to pass. These scenarios passed:
+      (::) passed scenarios (::)
+
+      features/passing_outline.feature:7:in `Scenario Outline: Passing, Examples (#1)'
+
+
+      """