opal-rspec 0.8.0.alpha3 → 1.0.0.alpha1

data/rspec-core/upstream/features/command_line/rake_task.feature

@@ -39,7 +39,7 @@ Feature: rake task
     When I run `rake`
     Then the output should match:
       """
-      (ruby|rbx) -I\S+ [\/\S]+\/exe\/rspec
+      (ruby(\d\.\d(.\d)?)?|rbx) -I\S+ [\/\S]+\/exe\/rspec
       """
     Then the exit status should be 0
 
@@ -122,7 +122,7 @@ Feature: rake task
     Then the exit status should be 0
     Then the output should match:
       """
-      (ruby|rbx) -I\S+ [\/\S]+\/exe\/rspec --pattern spec[\/\\*{,}]+_spec.rb --tag fast
+      (ruby(\d\.\d(.\d)?)?|rbx) -I\S+ [\/\S]+\/exe\/rspec --pattern spec[\/\\*{,}]+_spec.rb --tag fast
       """
 
   Scenario: Passing rake task arguments to the `rspec` command via `rspec_opts`
@@ -154,5 +154,5 @@ Feature: rake task
     Then the exit status should be 0
     Then the output should match:
       """
-      (ruby|rbx) -I\S+ [\/\S]+\/exe\/rspec --pattern spec[\/\\*{,}]+_spec.rb --tag fast
+      (ruby(\d\.\d(.\d)?)?|rbx) -I\S+ [\/\S]+\/exe\/rspec --pattern spec[\/\\*{,}]+_spec.rb --tag fast
       """

data/rspec-core/upstream/features/command_line/randomization.feature

@@ -34,10 +34,13 @@ Feature: Randomization can be reproduced across test runs
       is necessary to replicate a given test run's randomness.
 
   Background:
+    Given a file named ".rspec" with:
+      """
+      --require spec_helper
+      """
+
     Given a file named "spec/random_spec.rb" with:
       """ruby
-      require 'spec_helper'
-
       RSpec.describe 'randomized example' do
         it 'prints random numbers' do
           puts 5.times.map { rand(99) }.join("-")

data/rspec-core/upstream/features/command_line/ruby.feature

@@ -16,8 +16,12 @@ Feature: run with `ruby` command
         it "is < 2" do
           expect(1).to be < 2
         end
+
+        it "has an intentional failure" do
+          expect(1).to be > 2
+        end
       end
       """
     When I run `ruby example_spec.rb`
-    Then the output should contain "1 example, 0 failures"
-
+    Then the output should contain "2 examples, 1 failure"
+     And the output should contain "expect(1).to be > 2"

data/rspec-core/upstream/features/command_line/tag.feature

@@ -1,22 +1,24 @@
 Feature: `--tag` option
 
-  Use the `--tag` (or `-t`) option to filter the examples by tags.
+  Use the `--tag` (or `-t`) option to run examples that match a specified tag.
+  The tag can be a simple `name` or a `name:value` pair.
 
-  The tag can be a simple `name` or a `name:value` pair. In the first case,
-  examples with `:name => true` will be filtered. In the second case, examples
-  with `:name => value` will be filtered, where `value` is always a string. In
-  both cases, `name` is converted to a symbol.
-
-  Filters are represented internally as a hash, which means that you can't
-  specify multiple filters for the same key. If you try to exclude `:name => 'foo'`
-  and `:name => 'bar'`, you will only end up excluding `:name => 'bar'`.
+  If a simple `name` is supplied, only examples with `:name => true` will run.
+  If a `name:value` pair is given, examples with `name => value` will run,
+  where `value` is always a string. In both cases, `name` is converted to a symbol.
 
   Tags can also be used to exclude examples by adding a `~` before the tag. For
-  example `~tag` will exclude all examples marked with `:tag => true` and
+  example, `~tag` will exclude all examples marked with `:tag => true` and
   `~tag:value` will exclude all examples marked with `:tag => value`.
 
+  Filtering by tag uses a hash internally, which means that you can't specify
+  multiple filters for the same key. For instance, if you try to exclude
+  `:name => 'foo'` and `:name => 'bar'`, you will only end up excluding
+  `:name => 'bar'`.
+
   To be compatible with the Cucumber syntax, tags can optionally start with an
-  `@` symbol, which will be ignored.
+  `@` symbol, which will be ignored as part of the tag, e.g. `--tag @focus` is
+  treated the same as `--tag focus` and is expanded to `:focus => true`.
 
   Background:
     Given a file named "tagged_spec.rb" with:

data/rspec-core/upstream/features/command_line/warnings_option.feature

@@ -1,6 +1,6 @@
 Feature: `--warnings` option (run with warnings enabled)
 
-  You can use the `--warnings` option to run specs with warnings enabled
+  Use the `--warnings` option to run specs with warnings enabled.
 
   @unsupported-on-rbx
   Scenario:
@@ -8,20 +8,37 @@ Feature: `--warnings` option (run with warnings enabled)
       """ruby
       RSpec.describe do
         it 'generates warning' do
-          @undefined
+          $undefined
         end
       end
       """
     When I run `rspec --warnings example_spec.rb`
     Then the output should contain "warning"
 
+  @ruby-2-7
+  Scenario:
+    Given a file named "example_spec.rb" with:
+      """ruby
+      def foo(**kwargs)
+        kwargs
+      end
+
+      RSpec.describe do
+       it "should warn about keyword arguments with 'rspec -w'" do
+         expect(foo({a: 1})).to eq({a: 1})
+        end
+      end
+      """
+    When I run `rspec -w example_spec.rb`
+    Then the output should contain "warning"
+
   @unsupported-on-rbx
   Scenario:
     Given a file named "example_spec.rb" with:
       """ruby
       RSpec.describe do
         it 'generates warning' do
-          @undefined
+          $undefined
         end
       end
       """

data/rspec-core/upstream/features/configuration/backtrace_exclusion_patterns.feature

@@ -1,7 +1,21 @@
 Feature: Excluding lines from the backtrace
 
-  To reduce the noise when diagnosing failures, RSpec excludes matching lines
-  from backtraces. The default exclusion patterns are:
+  To reduce the noise when diagnosing failures, RSpec can exclude lines belonging to certain gems or matching given patterns.
+
+  If you want to filter out backtrace lines belonging to specific gems, you can use `config.filter_gems_from_backtrace` like so:
+
+  ```ruby
+  config.filter_gems_from_backtrace "ignored_gem", "another_ignored_gem",
+  ```
+
+  For more control over which lines to ignore, you can use the the `backtrace_exclusion_patterns` option to either replace the default exclusion patterns, or append your own, e.g.
+
+  ```ruby
+  config.backtrace_exclusion_patterns = [/first pattern/, /second pattern/]
+  config.backtrace_exclusion_patterns << /another pattern/
+  ```
+
+  The default exclusion patterns are:
 
   ```ruby
   /\/lib\d*\/ruby\//,
@@ -10,12 +24,8 @@ Feature: Excluding lines from the backtrace
   /lib\/rspec\/(core|expectations|matchers|mocks)/
   ```
 
-  This list can be modified or replaced with the `backtrace_exclusion_patterns`
-  option. Additionally, `rspec` can be run with the `--backtrace` option to skip
-  backtrace cleaning entirely.
+  Additionally, `rspec` can be run with the `--backtrace` option to skip backtrace cleaning entirely.
 
-  In addition, if you want to filter out backtrace lines from specific gems, you
-  can use `config.filter_gems_from_backtrace`.
 
   Scenario: Using default `backtrace_exclusion_patterns`
     Given a file named "spec/failing_spec.rb" with:
@@ -38,17 +48,13 @@ Feature: Excluding lines from the backtrace
         /spec_helper/
       ]
     end
-
-    def foo
-      "bar"
-    end
     """
     And a file named "spec/example_spec.rb" with:
     """ruby
     require 'spec_helper'
     RSpec.describe "foo" do
       it "returns baz" do
-        expect(foo).to eq("baz")
+        expect("foo").to eq("baz")
       end
     end
     """
@@ -57,55 +63,65 @@ Feature: Excluding lines from the backtrace
     And the output should contain "lib/rspec/expectations"
 
   Scenario: Appending to `backtrace_exclusion_patterns`
-    Given a file named "spec/matchers/be_baz_matcher.rb" with:
+    Given a file named "spec/support/assert_baz.rb" with:
     """ruby
-    RSpec::Matchers.define :be_baz do |_|
-      match do |actual|
-        actual == "baz"
-      end
+    require "support/really_assert_baz"
+
+    def assert_baz(arg)
+      really_assert_baz(arg)
+    end
+    """
+    And a file named "spec/support/really_assert_baz.rb" with:
+    """ruby
+    def really_assert_baz(arg)
+      expect(arg).to eq("baz")
     end
     """
     And a file named "spec/example_spec.rb" with:
     """ruby
+    require "support/assert_baz"
     RSpec.configure do |config|
-      config.backtrace_exclusion_patterns << /be_baz_matcher/
+      config.backtrace_exclusion_patterns << /really/
     end
 
     RSpec.describe "bar" do
       it "is baz" do
-        expect("bar").to be_baz
+        assert_baz("bar")
       end
     end
     """
     When I run `rspec`
     Then the output should contain "1 example, 1 failure"
-    But the output should not contain "be_baz_matcher"
+    And the output should contain "assert_baz"
+    But the output should not contain "really_assert_baz"
     And the output should not contain "lib/rspec/expectations"
 
-  Scenario: Running `rspec` with the `--backtrace` option
-    Given a file named "spec/matchers/be_baz_matcher.rb" with:
+  Scenario: Running `rspec` with `--backtrace` prints unfiltered backtraces
+    Given a file named "spec/support/custom_helper.rb" with:
     """ruby
-    RSpec::Matchers.define :be_baz do |_|
-      match do |actual|
-        actual == "baz"
-      end
+    def assert_baz(arg)
+      expect(arg).to eq("baz")
     end
     """
     And a file named "spec/example_spec.rb" with:
     """ruby
+    require "support/custom_helper"
+
     RSpec.configure do |config|
-      config.backtrace_exclusion_patterns << /be_baz_matcher/
+      config.backtrace_exclusion_patterns << /custom_helper/
     end
 
     RSpec.describe "bar" do
       it "is baz" do
-        expect("bar").to be_baz
+        assert_baz("bar")
       end
     end
     """
     When I run `rspec --backtrace`
     Then the output should contain "1 example, 1 failure"
-    And the output should not contain "be_baz_matcher"
+    And the output should contain "spec/support/custom_helper.rb:2:in `assert_baz'"
+    And the output should contain "lib/rspec/expectations"
+    And the output should contain "lib/rspec/core"
 
   Scenario: Using `filter_gems_from_backtrace` to filter the named gem
     Given a vendored gem named "my_gem" containing a file named "lib/my_gem.rb" with:

data/rspec-core/upstream/features/configuration/color.feature

@@ -0,0 +1,22 @@
+Feature: Windows may require additional solutions to display color
+
+  The output uses [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code) to show text in color.  Windows
+  systems (shells) often don't interpret those codes at all.
+
+  If you're on Windows and you see ANSI escape codes in the output
+  (something like `[1m [31m` ) and your text isn't in different colors,
+  you may need to install a utility so that your Windows shell will
+  interpret those codes correctly and show the colors.  Here are some
+  popular solutions:
+
+    * [ANSICON](https://github.com/adoxa/ansicon): ANSICON runs 'on top of' cmd or powershell. This is a very
+      popular solution. You can set it up so that it's always used whenever
+      you use cmd or powershell, or use it only at specific times.
+
+    * Alternatives to cmd.exe or powershell: [ConEmu](http://conemu.github.io/), [Console2](http://sourceforge.net/projects/console/),
+      [ConsoleZ](https://github.com/cbucher/console)
+
+    * Unix-like shells and utilities:  [cygwin](https://www.cygwin.com/), [babun](http://babun.github.io/index.html),
+      [MinGW](http://www.mingw.org/) (Minimalist GNU for Windows)
+
+  To find out more, search for information about those solutions.

data/rspec-core/upstream/features/configuration/custom_settings.feature

@@ -14,18 +14,14 @@ Feature: custom settings
           expect(RSpec.configuration.custom_setting).to be_nil
         end
 
-        it "acts false by default" do
-          expect(RSpec.configuration.custom_setting).to be_falsey
-        end
-
         it "is exposed as a predicate" do
-          expect(RSpec.configuration.custom_setting?).to be_falsey
+          expect(RSpec.configuration.custom_setting?).to be(false)
         end
 
         it "can be overridden" do
           RSpec.configuration.custom_setting = true
-          expect(RSpec.configuration.custom_setting).to be_truthy
-          expect(RSpec.configuration.custom_setting?).to be_truthy
+          expect(RSpec.configuration.custom_setting).to be(true)
+          expect(RSpec.configuration.custom_setting?).to be(true)
         end
       end
       """
@@ -41,17 +37,17 @@ Feature: custom settings
 
       RSpec.describe "custom setting" do
         it "is true by default" do
-          expect(RSpec.configuration.custom_setting).to be_truthy
+          expect(RSpec.configuration.custom_setting).to be(true)
         end
 
         it "is exposed as a predicate" do
-          expect(RSpec.configuration.custom_setting?).to be_truthy
+          expect(RSpec.configuration.custom_setting?).to be(true)
         end
 
         it "can be overridden" do
           RSpec.configuration.custom_setting = false
-          expect(RSpec.configuration.custom_setting).to be_falsey
-          expect(RSpec.configuration.custom_setting?).to be_falsey
+          expect(RSpec.configuration.custom_setting).to be(false)
+          expect(RSpec.configuration.custom_setting?).to be(false)
         end
       end
       """
@@ -71,11 +67,11 @@ Feature: custom settings
 
       RSpec.describe "custom setting" do
         it "returns the value set in the last cofigure block to get eval'd" do
-          expect(RSpec.configuration.custom_setting).to be_truthy
+          expect(RSpec.configuration.custom_setting).to be(true)
         end
 
         it "is exposed as a predicate" do
-          expect(RSpec.configuration.custom_setting?).to be_truthy
+          expect(RSpec.configuration.custom_setting?).to be(true)
         end
       end
       """

data/rspec-core/upstream/features/configuration/default_path.feature

@@ -5,7 +5,7 @@ Feature: Setting the default spec path
   This is supported by a `--default-path` option, which is set to `spec` by
   default. If you prefer to keep your specs in a different directory, or assign
   an individual file to `--default-path`, you can do so on the command line or
-  in a configuration file (`.rspec`, `~/.rspec`, or a custom file).
+  in a configuration file (for example `.rspec`).
 
   **NOTE:** this option is not supported on `RSpec.configuration`, as it needs to be
   set before spec files are loaded.

data/rspec-core/upstream/features/configuration/enable_global_dsl.feature

@@ -24,10 +24,11 @@ Feature: Global namespace DSL
 
   For backwards compatibility it defaults to `true`.
 
+  @allow-should-syntax
   Scenario: By default RSpec allows the DSL to be used globally
     Given a file named "spec/example_spec.rb" with:
       """ruby
-      RSpec.describe "specs here" do
+      describe "specs here" do
         it "passes" do
         end
       end
@@ -35,6 +36,19 @@ Feature: Global namespace DSL
    When I run `rspec`
    Then the output should contain "1 example, 0 failures"
 
+  @allow-should-syntax
+  Scenario: By default rspec/autorun allows the DSL to be used globally
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require 'rspec/autorun'
+      describe "specs here" do
+        it "passes" do
+        end
+      end
+      """
+   When I run `ruby spec/example_spec.rb`
+   Then the output should contain "1 example, 0 failures"
+
   Scenario: When exposing globally is disabled the top level DSL no longer works
     Given a file named "spec/example_spec.rb" with:
       """ruby

data/rspec-core/upstream/features/configuration/error_exit_code.feature

@@ -0,0 +1,52 @@
+Feature: error exit code
+
+  Use the `error_exit_code` option to set a custom exit code when RSpec fails outside an example.
+
+  ```ruby
+  RSpec.configure { |c| c.error_exit_code = 42 }
+  ```
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.error_exit_code = 42 }
+      """
+
+  Scenario: A erroring spec with the default exit code
+    Given a file named "spec/typo_spec.rb" with:
+      """ruby
+      RSpec.escribe "something" do # intentional typo
+        it "works" do
+          true
+        end
+      end
+      """
+    When I run `rspec spec/typo_spec.rb`
+    Then the exit status should be 1
+
+  Scenario: A erroring spec with a custom exit code
+    Given a file named "spec/typo_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      RSpec.escribe "something" do # intentional typo
+        it "works" do
+          true
+        end
+      end
+      """
+    When I run `rspec spec/typo_spec.rb`
+    And  the exit status should be 42
+
+
+  Scenario: Success running specs spec with a custom error exit code defined
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      RSpec.describe "something" do
+        it "works" do
+          true
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the exit status should be 0

data/rspec-core/upstream/features/configuration/fail_fast.feature

@@ -1,19 +1,13 @@
 Feature: fail fast
 
-  Use the `fail_fast` option to tell RSpec to abort the run on first failure:
+  Use the `fail_fast` option to tell RSpec to abort the run after N failures:
 
-  ```ruby
-  RSpec.configure { |c| c.fail_fast = true }
-  ```
-
-  Background:
+  Scenario: `fail_fast` with no failures (runs all examples)
     Given a file named "spec/spec_helper.rb" with:
       """ruby
-      RSpec.configure {|c| c.fail_fast = true}
+      RSpec.configure {|c| c.fail_fast = 1}
       """
-
-  Scenario: `fail_fast` with no failures (runs all examples)
-    Given a file named "spec/example_spec.rb" with:
+    And a file named "spec/example_spec.rb" with:
       """ruby
       RSpec.describe "something" do
         it "passes" do
@@ -27,7 +21,11 @@ Feature: fail fast
     Then the examples should all pass
 
   Scenario: `fail_fast` with first example failing (only runs the one example)
-    Given a file named "spec/example_spec.rb" with:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure {|c| c.fail_fast = 1}
+      """
+    And a file named "spec/example_spec.rb" with:
       """ruby
       require "spec_helper"
       RSpec.describe "something" do
@@ -43,7 +41,11 @@ Feature: fail fast
     Then the output should contain "1 example, 1 failure"
 
   Scenario: `fail_fast` with multiple files, second example failing (only runs the first two examples)
-    Given a file named "spec/example_1_spec.rb" with:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure {|c| c.fail_fast = 1}
+      """
+    And a file named "spec/example_1_spec.rb" with:
       """ruby
       require "spec_helper"
       RSpec.describe "something" do
@@ -77,3 +79,31 @@ Feature: fail fast
       """
     When I run `rspec spec`
     Then the output should contain "2 examples, 1 failure"
+
+
+  Scenario: `fail_fast 2` with 1st and 3rd examples failing (only runs the first 3 examples)
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure {|c| c.fail_fast = 2}
+      """
+    And a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+      RSpec.describe "something" do
+        it "fails once" do
+          fail
+        end
+
+        it "passes once" do
+        end
+
+        it "fails twice" do
+          fail
+        end
+
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb -fd`
+    Then the output should contain "3 examples, 2 failures"

data/rspec-core/upstream/features/configuration/fail_if_no_examples.feature

@@ -0,0 +1,31 @@
+Feature: fail if no examples
+
+  Use the `fail_if_no_examples` option to make RSpec exit with a failure status (by default 1) if there are no examples. Using this option, it is recommended to add a `--require spec_helper` option to `.rspec` file to ensure the `fail_if_no_examples` option is set even if no spec files are loaded.
+
+  This option may be particularly useful when you happen to not run RSpec tests locally, but rely on CI to do this. This prevents from false positive builds, when you expected some RSpec examples to be run, but none were run. Such a situation may be caused by your misconfiguration or regression/major changes in RSpec.
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.fail_if_no_examples = true }
+      """
+    Given a file named ".rspec" with:
+      """ruby
+      --require spec_helper
+      """
+    Given a file named "spec/some.spec.rb" with:
+      """ruby
+      RSpec.describe 'something' do
+        it 'succeeds' do
+          true
+        end
+      end
+      """
+
+  Scenario: Examples file name is not matched by RSpec pattern, thus there are no examples run
+    When I run `rspec`
+    Then it should fail with "0 examples, 0 failures"
+
+  Scenario: Examples file name is matched by RSpec pattern, 1 example is run
+    When I run `rspec --pattern spec/**/*.spec.rb`
+    Then it should pass with "1 example, 0 failures"

data/rspec-core/upstream/features/configuration/failure_exit_code.feature

@@ -37,6 +37,32 @@ Feature: failure exit code
     When I run `rspec spec/example_spec.rb`
     Then the exit status should be 42
 
+  Scenario: An error running specs spec with a custom exit code
+    Given a file named "spec/typo_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      RSpec.escribe "something" do # intentional typo
+        it "works" do
+          true
+        end
+      end
+      """
+    When I run `rspec spec/typo_spec.rb`
+    Then the exit status should be 42
+
+  Scenario: Success running specs spec with a custom exit code defined
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      RSpec.describe "something" do
+        it "works" do
+          true
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the exit status should be 0
+
   Scenario: Exit with the default exit code when an `at_exit` hook is added upstream
     Given a file named "exit_at_spec.rb" with:
       """ruby

data/rspec-core/upstream/features/configuration/overriding_global_ordering.feature

@@ -11,7 +11,7 @@ Feature: Overriding global ordering
   `:global`, it will be the global default, used by all groups that do not have
   `:order` metadata (and by RSpec to order the top-level groups).
 
-  Scenario: Running a specific examples group in order
+  Scenario: Running a specific example group in order
     Given a file named "order_dependent_spec.rb" with:
       """ruby
       RSpec.describe "examples only pass when they are run in order", :order => :defined do

data/rspec-core/upstream/features/configuration/pattern.feature

@@ -45,7 +45,7 @@ Feature: pattern
     Given a file named "spec/spec_helper.rb" with:
       """ruby
       RSpec.configure do |config|
-        config.pattern << ',**/*.spec'
+        config.pattern += ',**/*.spec'
       end
       """
     And a file named "spec/two_examples.spec" with:

data/rspec-core/upstream/features/configuration/profile.feature

@@ -218,3 +218,28 @@ Feature: Profile examples
     When I run `rspec spec --fail-fast --profile`
     Then the output should not contain "Top 2 slowest examples"
     And the output should not contain "example 1"
+
+  Scenario: Using `--profile` with slow before hooks includes hook execution time
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      RSpec.describe "slow before context hook" do
+        before(:context) do
+          sleep 0.2
+        end
+
+        context "nested" do
+          it "example" do
+            expect(10).to eq(10)
+          end
+        end
+      end
+
+      RSpec.describe "slow example" do
+        it "slow example" do
+          sleep 0.1
+          expect(10).to eq(10)
+        end
+      end
+      """
+    When I run `rspec spec --profile 1`
+    Then the output should report "slow before context hook" as the slowest example group