cucumber 2.3.3 → 2.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c53e4902ca73f5999ff60be26b1817622c631974
-  data.tar.gz: b4f35193ddd03bacefefd3483184fb9f88c1f624
+  metadata.gz: 1cd101b22f43dfd823d81914b2e7bbcf3c26e545
+  data.tar.gz: e39d9e9d47fc18abc4f2534f6da6da5cb8bc32c2
 SHA512:
-  metadata.gz: 09376bab164a61f983d2bd94c58f3621b7c773378ccfd5df577dbc76349b1d26c4da2a7d95557b65c8636aee403c08291d611124d81562f9824cd8b61acdd420
-  data.tar.gz: 928438ab720c2b6b18ceeb2f7b13b8df82d733fcf399095a4f5b7c68f4ca1601487a8661bff4d6c36c71074464bd36ba0884c87311023ef703c2d2ab5b9ed34b
+  metadata.gz: 5cadaad2e95ce0da02a2a12a4ac590af92eaa0424569cd393a7d0953159da1159401c402943be08fb51d9b2eec5661f4c75d889749716a647a88ae0d41f05376
+  data.tar.gz: 36b919d9c5a50da9426a058923a1821c1f3cdfea2ad63fda1c1a1651e6da141b3034cff95d38a9f4733598dd8eedcf447205c7427d64870f6aa45e1b6658cefd

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,48 @@
+<!-- These sections are meant as guidance for you, to help you give the kind of information we'll need to help with your issue. If a section  doesn't seem to fit, just skip it.
+
+In general: Please provide as much information as you can to help us solving your problem -->
+
+## Summary
+
+<!--- Provide a general summary description of the issue -->
+
+## Expected Behavior
+
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+<!--- Feel free to use Given / Then / Then if that helps, but please add some plain-language context too -->
+
+## Current Behavior
+
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+<!--- If you have got some output place it in the code block below. Otherwise remove it. -->
+~~~
+~~~
+
+## Possible Solution
+
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context & Motivation
+
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+
+<!--- If you're reporting a bug, include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+* Operating System and version:
+* Link to your project:

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,39 @@
+<!-- These sections are meant as guidance for you. If something doesn't fit, you can just skip it. -->
+
+## Summary
+
+<!--- Provide a general summary description of your changes -->
+
+## Details
+
+<!--- Describe your changes in detail -->
+
+## Motivation and Context
+
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## How Has This Been Tested?
+
+<!--- Please add tests for changes to the code, otherwise we probably won't merge it -->
+
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, tests ran to see how -->
+<!--- your change affects other areas of the code, etc. -->
+
+## Screenshots (if appropriate):
+
+## Types of changes
+
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+## Checklist:
+
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] I've added tests for my code
+- [ ] My change requires a change to the documentation.
+- [ ] I have updated the documentation accordingly.

data/.travis.yml

@@ -1,6 +1,7 @@
 sudo: false
 
 rvm:
+  - 2.3.0
   - 2.2
   - 2.1
   - 2.0
@@ -11,14 +12,12 @@ rvm:
 branches:
   only:
     - master
+    - resolve-issue-882
     - v1.3.x-bugfix
+    - v2.x-bugfix
 
 before_install:
   - gem update bundler
 
 notifications:
-  email:
-    - cukes-devs@googlegroups.com
-  webhooks:
-    urls: # gitter
-      - https://webhooks.gitter.im/e/dc010332f9d40fcc21c4
+  email: false

data/Gemfile

@@ -8,6 +8,8 @@ unless ENV['CUCUMBER_USE_RELEASED_CORE']
     gem 'cucumber-core', :path => core_path
     gem 'cucumber-wire', :path => wire_path
   else
-    gem 'cucumber-core', :git => "git://github.com/cucumber/cucumber-ruby-core.git"
+    gem 'cucumber-core', :git => "https://github.com/cucumber/cucumber-ruby-core.git", :branch => 'v1.x-bugfix'
   end
 end
+
+gem 'mime-types', '~>2.99'

data/History.md

@@ -1,9 +1,25 @@
-## [In Git](https://github.com/cucumber/cucumber-ruby/compare/v2.3.3...master)
+## [In Git](https://github.com/cucumber/cucumber-ruby/compare/v2.4.0...v2.x-bugfix)
 
 ### New Features
 
 ### Bugfixes
 
+## [v2.4.0](https://github.com/cucumber/cucumber-ruby/compare/v2.3.3...v2.4.0)
+
+### New Features
+
+* Update to Gherkin v4.0 (@brasmusson)
+
+### Bugfixes
+
+* Use HTTPS instead of Git as transport protocol ([#960](https://github.com/cucumber/cucumber-ruby/pull/960))
+* Make random order stable and platform independent ([#974](https://github.com/cucumber/cucumber-ruby/pull/974), closes [#971](https://github.com/cucumber/cucumber-ruby/issues/971))
+* Run scenarios in fully random order ([#970](https://github.com/cucumber/cucumber-ruby/pull/970) @threedaymonk)
+* Adding Test Step in AfterStep hook. ([#931](https://github.com/cucumber/cucumber-ruby/pull/931) @t-morgan)
+* Handle even more exotic rerun file formats seen in the wild ([#928](https://github.com/cucumber/cucumber-ruby/pull/928) @mcrmfc)
+* Allow Rake task to accept multiple profiles. ([#907](https://github.com/cucumber/cucumber-ruby/pull/907) @jasonkarns)
+* Let the JUnit formatter handle running test cases for different features interweaved ([#952](https://github.com/cucumber/cucumber-ruby/issues/952) @brasmusson)
+
 ## [v2.3.3](https://github.com/cucumber/cucumber-ruby/compare/v2.3.2...v2.3.3)
 
 Added a message pointing users to [The Great Cucumber and BDD Census of 2016](https://cucumber.typeform.com/to/kjrSc2?audience=cucumber-ruby) to the installer message. Please take a few moments to help us all learn more about how you're using Cucumber and BDD.
@@ -160,7 +176,7 @@ could cause breaking changes for users of undocumented APIs. Hence the minor ver
 ## [v2.0.0.rc.1](https://github.com/cucumber/cucumber-ruby/compare/v2.0.0.beta.5...v2.0.0.rc.1)
 
 ### Removed Features
-  
+
 * Removed support for IronRuby (@tooky @mattwynne)
 
 ### New Features

data/LICENSE

@@ -1,6 +1,6 @@
 The MIT License
 
-Copyright (c) 2008-2013 Aslak Hellesøy
+Copyright (c) Aslak Hellesøy
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.md

@@ -6,7 +6,6 @@
 
 # Cucumber
 
-
 Cucumber is a tool for running automated tests written in plain language. Because they're
 written in plain language, they can be read by anyone on your team. Because they can be 
 read by anyone, you can use them to help improve communication, collaboration and trust on
@@ -23,6 +22,10 @@ Where to get more info:
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for info on contributing to Cucumber.
 
+## Code of Conduct
+
+Everyone interacting in this codebase and issue tracker is expected to follow the Cucumber [code of conduct](https://github.com/cucumber/cucumber/blob/master/CODE_OF_CONDUCT.md).
+
 ## Copyright
 
-Copyright (c) 2008-2015 Aslak Hellesøy and Contributors. See LICENSE for details.
+Copyright (c) Aslak Hellesøy and Contributors. See LICENSE for details.

data/cucumber.gemspec

@@ -10,21 +10,10 @@ Gem::Specification.new do |s|
   s.homepage    = "http://cukes.info"
   s.platform    = Gem::Platform::RUBY
   s.required_ruby_version = ">= 1.9.3"
-  s.post_install_message = %{We need your help.
-    
-Please take a few minutes to fill out our survey and help us understand how BDD and Cucumber are used in the wild.
-  
-  http://tinyurl.com/zk9jyrf
-
-Thanks!
-
-♡ The Cucumber Team ♡
-}
-
-  s.add_dependency 'cucumber-core', '~> 1.4.0'
+  s.add_dependency 'cucumber-core', '~> 1.5.0'
   s.add_dependency 'builder', '>= 2.1.2'
   s.add_dependency 'diff-lcs', '>= 1.1.3'
-  s.add_dependency 'gherkin', '~> 3.2.0'
+  s.add_dependency 'gherkin', '~> 4.0'
   s.add_dependency 'multi_json', '>= 1.7.5', '< 2.0'
   s.add_dependency 'multi_test', '>= 0.1.2'
   s.add_dependency 'cucumber-wire', '~> 0.0.1'

data/examples/i18n/eo/features/adicio.feature

@@ -1,14 +1,14 @@
 # language: eo
 Trajto: Adicio
   Por eviti stultajn erarojn
-  Kiel stultulo in matematiko
-  Mi volas ke mi estu ebla adicii du nombrojn
+  Kiel stultulo pri matematiko
+  Mi volas adicii du nombrojn
 
-  Konturo de la scenaro: Adiciu du nombrojn
-    Donitaĵo mi entajpas <nombro_1> en kalkulilo
-    Kaj mi entajpas <nombro_2> en kalkulilo
+  Kazo-skizo: Adiciu du nombrojn
+    Komence mi entajpas <nombro_1> en la kalkulilon
+    Kaj mi entajpas <nombro_2> en la kalkulilon
     Se mi premas <butono>
-    Do la rezulto devas esti <rezulto>
+    Do la rezulto estu <rezulto>
 
   Ekzemploj:
     | nombro_1 | nombro_2 | butono | rezulto |

data/examples/i18n/eo/features/divido.feature

@@ -1,10 +1,10 @@
 # language: eo
 Trajto: Divido
   Por eviti stultajn erarojn
-  Uzantoj devas havi eblecon kalkuli frakcion
+  Uzantoj kapablu kalkuli frakciojn
 
-  Scanaro: Simplaj nombroj
-    * mi entajpis 3 en kalkulilo
-    * mi entajpis 2 en kalkulilo
-    * mi premis dividi
-    * la rezulto devas esti 1.5
+  Kazo: Simplaj nombroj
+    * mi entajpas 3 en la kalkulilon
+    * mi entajpas 2 en la kalkulilon
+    * mi premis divide
+    * la rezulto estu 1.5

data/examples/i18n/eo/features/step_definitions/calculator_steps.rb

@@ -11,7 +11,7 @@ end
 After do
 end
 
-Given /mi entajpas (\d+) en kalkulilo/ do |n|
+Given /mi entajpas (\d+) en la kalkulilon/ do |n|
   @calc.push n.to_i
 end
 
@@ -19,6 +19,6 @@ When /mi premas (\w+)/ do |op|
   @result = @calc.send op
 end
 
-Then /la rezulto devas esti (.*)/ do |result|
+Then /la rezulto estu (.*)/ do |result|
   @result.should == result.to_f
 end

data/features/docs/cli/randomize.feature

@@ -9,17 +9,36 @@ Feature: Randomize
   you can reproduce that run by using the seed that's printed at the end of
   the test run.
 
+  For a given seed, the order of scenarios is constant, i.e. if step A runs
+  before step B, it will always run before step B even if other steps are
+  skipped.
+
   Background:
-    Given a file named "features/bad_practice.feature" with:
+    Given a file named "features/bad_practice_part_1.feature" with:
       """
-      Feature: Bad practice
+      Feature: Bad practice, part 1
         
         Scenario: Set state
           Given I set some state
       
-        Scenario: Depend on state
+        Scenario: Depend on state from a preceding scenario
+          When I depend on the state
+      """
+    And a file named "features/bad_practice_part_2.feature" with:
+      """
+      Feature: Bad practice, part 2
+
+        Scenario: Depend on state from a preceding feature
           When I depend on the state
       """
+    And a file named "features/unrelated.feature" with:
+      """
+      Feature: Unrelated
+
+        @skipme
+        Scenario: Do something unrelated
+          When I do something
+      """
     And a file named "features/step_definitions/steps.rb" with:
       """
       Given(/^I set some state$/) do
@@ -29,6 +48,9 @@ Feature: Randomize
       Given(/^I depend on the state$/) do
         raise "I expect the state to be set!" unless $global_state == "set"
       end
+
+      Given(/^I do something$/) do
+      end
       """
 
   Scenario: Run scenarios in order
@@ -37,28 +59,82 @@ Feature: Randomize
 
   @spawn
   Scenario: Run scenarios randomized
-    When I run `cucumber --order random:41515 -q`
+    When I run `cucumber --order random:41544 -q`
     Then it should fail
     And the stdout should contain exactly:
       """
-      Feature: Bad practice
-      
-        Scenario: Depend on state
+      Feature: Bad practice, part 1
+
+        Scenario: Depend on state from a preceding scenario
           When I depend on the state
             I expect the state to be set! (RuntimeError)
             ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
-            features/bad_practice.feature:7:in `When I depend on the state'
+            features/bad_practice_part_1.feature:7:in `When I depend on the state'
+
+      Feature: Unrelated
+
+        @skipme
+        Scenario: Do something unrelated
+          When I do something
+
+      Feature: Bad practice, part 2
+
+        Scenario: Depend on state from a preceding feature
+          When I depend on the state
+            I expect the state to be set! (RuntimeError)
+            ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
+            features/bad_practice_part_2.feature:4:in `When I depend on the state'
+
+      Feature: Bad practice, part 1
 
         Scenario: Set state
           Given I set some state
       
       Failing Scenarios:
-      cucumber features/bad_practice.feature:6
-    
-      2 scenarios (1 failed, 1 passed)
-      2 steps (1 failed, 1 passed)
-      
-      Randomized with seed 41515
-      
+      cucumber features/bad_practice_part_1.feature:6
+      cucumber features/bad_practice_part_2.feature:3
+
+      4 scenarios (2 failed, 2 passed)
+      4 steps (2 failed, 2 passed)
+
+      Randomized with seed 41544
+
+      """
+
+  @spawn
+  Scenario: Run scenarios randomized with some skipped
+    When I run `cucumber --tags ~@skipme --order random:41544 -q`
+    Then it should fail
+    And the stdout should contain exactly:
       """
+      Feature: Bad practice, part 1
+
+        Scenario: Depend on state from a preceding scenario
+          When I depend on the state
+            I expect the state to be set! (RuntimeError)
+            ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
+            features/bad_practice_part_1.feature:7:in `When I depend on the state'
+
+      Feature: Bad practice, part 2
+
+        Scenario: Depend on state from a preceding feature
+          When I depend on the state
+            I expect the state to be set! (RuntimeError)
+            ./features/step_definitions/steps.rb:6:in `/^I depend on the state$/'
+            features/bad_practice_part_2.feature:4:in `When I depend on the state'
+
+      Feature: Bad practice, part 1
+
+        Scenario: Set state
+          Given I set some state
+
+      Failing Scenarios:
+      cucumber features/bad_practice_part_1.feature:6
+      cucumber features/bad_practice_part_2.feature:3
 
+      3 scenarios (2 failed, 1 passed)
+      3 steps (2 failed, 1 passed)
+
+      Randomized with seed 41544
+
+      """

data/features/docs/cli/retry_failing_tests.feature

@@ -0,0 +1,32 @@
+@wip
+Feature: Retry failing tests
+
+  Retry gives you a way to get through flaky tests that usually pass after a few runs.
+  This gives a development team a way forward other than disabling a valuable test.
+  
+  - Specify max retry count in option
+  - Output information to the screen
+  - Output retry information in test report
+  
+  Questions:
+  use a tag for flaky tests?  Global option to retry any test that fails?
+  
+  Background:
+    Given a scenario "Flakey" that fails once, then passes
+    And a scenario "Shakey" that fails twice, then passes
+    And a scenario "Solid" that passes
+    And a scenario "No Dice" that fails
+  
+  Scenario:
+    When I run `cucumber -q --retry 1`
+    Then it should fail with:
+      """
+      4 scenarios (2 passed, 2 failed)
+      """
+
+  Scenario:
+    When I run `cucumber -q --retry 2`
+    Then it should pass with:
+      """
+      4 scenarios (3 passed, 1 failed)
+      """