cucumber 1.3.20 → 2.0.0.beta.1

data/examples/i18n/fr/Rakefile

@@ -3,4 +3,6 @@ require 'cucumber/rake/task'
 
 Cucumber::Rake::Task.new do |t|
   t.cucumber_opts = %w{--format pretty}
-end
+end
+
+task default: :cucumber

data/examples/i18n/fr/features/step_definitions/calculatrice_steps.rb

@@ -20,11 +20,11 @@ Lorsqu /on tape additionner/ do
 end
 
 Alors /le résultat affiché doit être (\d*)/ do |result|
-  result.to_i.should == @expected_result
+  expect result.to_i == @expected_result
 end
 
 Alors /le résultat doit être (\d*)/ do |result|
-  result.to_i.should == @expected_result
+  expect result.to_i == @expected_result
 end
 
 Soit /^que je tape sur la touche "\+"$/ do

data/examples/i18n/zh-CN/features/{step_definitons → step_definitions}/calculator_steps.rb

@@ -11,16 +11,16 @@ end
 After do
 end
 
-Given /我已经在计算器里输入(\d+)/ do |n|
+Given /在计算器上输入(\d+)/ do |n|
   @calc.push n.to_i
 end
 
-When /我按(.*)按钮/ do |op|
-  if op == '相加'
+When /按(.*)键/ do |op|
+  if op == '加号'
     @result = @calc.send "add"
   end
 end
 
-Then /我应该在屏幕上看到的结果是(.*)/ do |result|
+Then /屏幕上显示的结果应该是是(.*)/ do |result|
   @result.should == result.to_f
 end

data/{legacy_features → features/docs}/api/list_step_defs_as_json.feature

@@ -1,16 +1,18 @@
+@spawn
 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
-  
+
+  Background:
+    Given a directory named "features"
+
   Scenario: Two Ruby step definitions, in the same file
-    Given a file named "features/step_definitions/foo_steps.rb" with:
+    Given a file named "features/step_definitions/steps.rb" with:
       """
-      Given(/foo/i) {}
-      Given(/b.r/xm) {}
+      Given(/foo/i)  { }
+      Given(/b.r/xm) { }
       """
     When I run the following Ruby code:
       """
@@ -18,8 +20,7 @@ Feature: List step defs as json
       puts Cucumber::StepDefinitions.new.to_json
       
       """
-    Then it should pass
-    And the output should contain the following JSON:
+    Then it should pass with JSON:
       """
       [
         {"source": "foo", "flags": "i"},
@@ -28,10 +29,10 @@ Feature: List step defs as json
       """
 
   Scenario: Non-default directory structure
-    Given a file named "my_weird/place/foo_steps.rb" with:
+    Given a file named "my_weird/place/steps.rb" with:
       """
-      Given(/foo/) {}
-      Given(/b.r/x) {}
+      Given(/foo/)  { }
+      Given(/b.r/x) { }
       """
     When I run the following Ruby code:
       """
@@ -39,8 +40,7 @@ Feature: List step defs as json
       puts Cucumber::StepDefinitions.new(:autoload_code_paths => ['my_weird']).to_json
       
       """
-    Then it should pass
-    And the output should contain the following JSON:
+    Then it should pass with JSON:
       """
       [
         {"source": "foo", "flags": ""},

data/{legacy_features → features/docs}/api/run_cli_main_with_existing_runtime.feature

@@ -1,3 +1,4 @@
+@spawn
 Feature: Run Cli::Main with existing Runtime
 
   This is the API that Spork uses. It creates an existing runtime then
@@ -5,19 +6,13 @@ Feature: Run Cli::Main with existing Runtime
   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 the standard step definitions
       Given a file named "features/success.feature" with:
         """
         Feature: 
           Scenario: 
-            Given I pass
+            Given this step passes
         """
       When I run the following Ruby code:
         """
@@ -30,5 +25,5 @@ Feature: Run Cli::Main with existing Runtime
       Then it should pass
       And the output should contain:
         """
-        Given I pass
-        """
+        Given this step passes
+        """

data/features/{backtraces.feature → docs/cli/backtraces.feature}

@@ -1,4 +1,5 @@
 Feature: Backtraces
+
   In order to discover errors quickly
   As a cuker
   I want to see backtraces for failures
@@ -30,7 +31,6 @@ Feature: Backtraces
         Scenario: Example # features/failing_hard.feature:2
           Given failing   # features/step_definitions/steps.rb:4
              (Java::JavaLang::UnsupportedOperationException)
-            java.util.AbstractList.add(java/util/AbstractList.java:148)
-            java.util.AbstractList.add(java/util/AbstractList.java:108)
+            java.util.AbstractList.add(java/util/AbstractList.java:
       """
 

data/features/docs/cli/dry_run.feature

@@ -0,0 +1,25 @@
+Feature: Dry Run
+  - Invokes formatters without executing the steps.
+  - This also omits the loading of your support/env.rb file if it exists.
+
+  Scenario: With a failing step
+    Given a file named "features/test.feature" with:
+      """
+      Feature: test
+        Scenario:
+          Given this step fails
+      """
+    And the standard step definitions
+    When I run `cucumber --dry-run`
+    Then it should pass with exactly:
+      """
+      Feature: test
+
+        Scenario:               # features/test.feature:2
+          Given this step fails # features/step_definitions/steps.rb:4
+
+      1 scenario (1 skipped)
+      1 step (1 skipped)
+      0m0.012s
+
+      """

data/features/docs/cli/exclude_files.feature

@@ -0,0 +1,19 @@
+Feature: Excluding ruby and feature files from runs
+  Developers are able to easily exclude files from cucumber runs
+  This is a nice feature to have in conjunction with profiles, so you can exclude
+  certain environment files from certain runs.
+
+  Scenario: exclude ruby files
+    Given an empty file named "features/support/dont_require_me.rb"
+    And an empty file named "features/step_definitions/fooz.rb"
+    And an empty file named "features/step_definitions/foof.rb"
+    And an empty file named "features/step_definitions/foot.rb"
+    And an empty file named "features/support/require_me.rb"
+
+    When I run `cucumber features -q --verbose --exclude features/support/dont --exclude foo[zf]`
+
+    Then "features/support/require_me.rb" should be required
+    And "features/step_definitions/foot.rb" should be required
+    And "features/support/dont_require_me.rb" should not be required
+    And "features/step_definitions/foof.rb" should not be required
+    And "features/step_definitions/fooz.rb" should not be required

data/features/docs/cli/execute_with_tag_filter.feature

@@ -0,0 +1,117 @@
+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/test.feature" with:
+      """
+      @feature
+      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/test.feature`
+    Then it should pass with:
+      """
+      @feature
+      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/test.feature`
+    Then it should pass with:
+      """
+      @feature
+      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)
+
+      """
+
+  Scenario: Negative tags
+    When I run `cucumber -q -t ~@three features/test.feature`
+    Then it should pass with:
+      """
+      @feature
+      Feature: Sample
+
+        @one
+        Scenario: Another Example
+          Given passing
+
+        @ignore
+        Scenario: And yet another Example
+
+      2 scenarios (1 undefined, 1 passed)
+      1 step (1 undefined)
+      """
+
+  Scenario: Run with limited tag count, blowing it on scenario
+     When I run `cucumber -q --no-source --tags @one:1 features/test.feature`
+     Then it fails before running features with:
+       """
+       @one occurred 2 times, but the limit was set to 1
+         features/test.feature:5
+         features/test.feature:9
+       """
+
+  Scenario: Run with limited tag count, blowing it via feature inheritance
+     When I run `cucumber -q --no-source --tags @feature:1 features/test.feature`
+     Then it fails before running features with:
+       """
+       @feature occurred 4 times, but the limit was set to 1
+         features/test.feature:5
+         features/test.feature:9
+         features/test.feature:13
+         features/test.feature:17
+       """
+
+  Scenario: Run with limited tag count using negative tag, blowing it via a tag that is not run
+     When I run `cucumber -q --no-source --tags ~@one:1 features/test.feature`
+     Then it fails before running features with:
+       """
+       @one occurred 2 times, but the limit was set to 1
+       """
+
+  Scenario: Limiting with tags which do not exist in the features
+    Originally added to check [Lighthouse bug #464](https://rspec.lighthouseapp.com/projects/16211/tickets/464).
+
+    When I run `cucumber -q -t @i_dont_exist features/test.feature`
+    Then it should pass

data/features/docs/cli/randomize.feature

@@ -0,0 +1,46 @@
+Feature: Randomize
+
+  Use the `--order random` switch to run scenarios in random order.
+
+  This is especially helpful for detecting situations where you have state
+  leaking between scenarios, which can cause flickering or fragile tests.
+
+  If you do find a randmon run that exposes dependencies between your tests,
+  you can reproduce that run by using the seed that's printed at the end of
+  the test run.
+
+  Background:
+    Given a file named "features/bad_practice.feature" with:
+      """
+      Feature: Bad practice
+        
+        Scenario: Set state
+          Given I set some state
+      
+        Scenario: Depend on state
+          When I depend on the state
+      """
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given(/^I set some state$/) do
+        $global_state = "set"
+      end
+
+      Given(/^I depend on the state$/) do
+        raise "I expect the state to be set!" unless $global_state == "set"
+      end
+      """
+
+  Scenario: Run scenarios in order
+    When I run `cucumber`
+    Then it should pass
+
+  @spawn
+  Scenario: Run scenarios randomized
+    When I run `cucumber --order random:41515`
+    Then it should fail
+    And the stdout should contain:
+      """
+      Randomized with seed 41515
+      """
+

data/features/docs/cli/require.feature

@@ -0,0 +1,27 @@
+Feature: Requiring extra step files
+
+  Cucumber allows you to require extra files using the `-r` option.
+
+  Scenario:
+    Given a file named "features/test.feature" with:
+      """
+      Feature: Sample
+        Scenario: Sample
+          Given found in extra file
+      """
+    And a file named "tmp/extras.rb" with:
+      """
+      Given(/^found in extra file$/) { }
+      """
+    When I run `cucumber -q -r tmp/extras.rb features/test.feature`
+    Then it should pass with:
+      """
+      Feature: Sample
+
+        Scenario: Sample
+          Given found in extra file
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+      """
+