opal-rspec 0.7.0.rc.1 → 0.7.0.rc.2

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

@@ -0,0 +1,43 @@
+Feature: exclude_pattern
+
+  Use the `--exclude-pattern` option to tell RSpec to skip looking for specs in files
+  that match the pattern specified.
+
+  Background:
+    Given a file named "spec/models/model_spec.rb" with:
+      """ruby
+      RSpec.describe "two specs here" do
+        it "passes" do
+        end
+
+        it "passes too" do
+        end
+      end
+      """
+    And a file named "spec/features/feature_spec.rb" with:
+      """ruby
+      RSpec.describe "only one spec" do
+        it "passes" do
+        end
+      end
+      """
+
+  Scenario: By default, RSpec runs files that match `"**/*_spec.rb"`
+   When I run `rspec`
+   Then the output should contain "3 examples, 0 failures"
+
+  Scenario: The `--exclude-pattern` flag makes RSpec skip matching files
+   When I run `rspec --exclude-pattern "**/models/*_spec.rb"`
+   Then the output should contain "1 example, 0 failures"
+
+  Scenario: The `--exclude-pattern` flag can be used to pass in multiple patterns, separated by comma
+   When I run `rspec --exclude-pattern "**/models/*_spec.rb, **/features/*_spec.rb"`
+   Then the output should contain "0 examples, 0 failures"
+
+  Scenario: The `--exclude-pattern` flag accepts shell style glob unions
+   When I run `rspec --exclude-pattern "**/{models,features}/*_spec.rb"`
+   Then the output should contain "0 examples, 0 failures"
+
+  Scenario: The `--exclude-pattern` flag can be used with the `--pattern` flag
+   When I run `rspec --pattern "spec/**/*_spec.rb" --exclude-pattern "spec/models/*_spec.rb"`
+   Then the output should contain "1 example, 0 failures"

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

@@ -0,0 +1,79 @@
+Feature: fail fast
+
+  Use the `fail_fast` option to tell RSpec to abort the run on first failure:
+
+  ```ruby
+  RSpec.configure { |c| c.fail_fast = true }
+  ```
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure {|c| c.fail_fast = true}
+      """
+
+  Scenario: `fail_fast` with no failures (runs all examples)
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      RSpec.describe "something" do
+        it "passes" do
+        end
+
+        it "passes too" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    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:
+      """ruby
+      require "spec_helper"
+      RSpec.describe "something" do
+        it "fails" do
+          fail
+        end
+
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb -fd`
+    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:
+      """ruby
+      require "spec_helper"
+      RSpec.describe "something" do
+        it "passes" do
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+
+      RSpec.describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    And a file named "spec/example_2_spec.rb" with:
+      """ruby
+      require "spec_helper"
+      RSpec.describe "something" do
+        it "passes" do
+        end
+      end
+
+      RSpec.describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the output should contain "2 examples, 1 failure"

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

@@ -0,0 +1,53 @@
+Feature: failure exit code
+
+  Use the `failure_exit_code` option to set a custom exit code when RSpec fails.
+
+  ```ruby
+  RSpec.configure { |c| c.failure_exit_code = 42 }
+  ```
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.failure_exit_code = 42 }
+      """
+
+  Scenario: A failing spec with the default exit code
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      RSpec.describe "something" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the exit status should be 1
+
+  Scenario: A failing spec with a custom exit code
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      RSpec.describe "something" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the exit status should be 42
+
+  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
+      require 'rspec/autorun'
+      at_exit { exit(0) }
+
+      RSpec.describe "exit 0 at_exit ignored" do
+        it "does not interfere with the default exit code" do
+          fail
+        end
+      end
+      """
+    When I run `ruby exit_at_spec.rb`
+    Then the exit status should be 1

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

@@ -0,0 +1,5 @@
+Feature: set the order and/or seed
+
+  You can set the order to run specs and specify a seed if you are running the
+  specs using the 'random' ordering. See [the documentation on the `--order`
+  command line option](../command-line/order) for more on this.

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

@@ -0,0 +1,27 @@
+Feature: Custom output stream
+
+  Define a custom output stream (default `$stdout`).  Aliases: `:output`,
+  `:out`.
+
+  ```ruby
+  RSpec.configure { |c| c.output_stream = File.open('saved_output', 'w') }
+  ```
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.output_stream = File.open('saved_output', 'w') }
+      """
+
+  Scenario: Redirecting output
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      RSpec.describe "an example" do
+        it "passes" do
+          true
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the file "saved_output" should contain "1 example, 0 failures"

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

@@ -0,0 +1,90 @@
+Feature: Overriding global ordering
+
+  You can customize how RSpec orders examples and example groups. For an
+  individual group, you can control it by tagging it with `:order` metadata:
+
+    * `:defined` runs the examples (and sub groups) in defined order
+    * `:random` runs them in random order
+
+  If you have more specialized needs, you can register your own ordering using
+  the `register_ordering` configuration option. If you register an ordering as
+  `: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
+    Given a file named "order_dependent_spec.rb" with:
+      """ruby
+      RSpec.describe "examples only pass when they are run in order", :order => :defined do
+        before(:context) { @list = [] }
+
+        it "passes when run first" do
+          @list << 1
+          expect(@list).to eq([1])
+        end
+
+        it "passes when run second" do
+          @list << 2
+          expect(@list).to eq([1, 2])
+        end
+
+        it "passes when run third" do
+          @list << 3
+          expect(@list).to eq([1, 2, 3])
+        end
+      end
+      """
+    When I run `rspec order_dependent_spec.rb --order random:1`
+    Then the examples should all pass
+
+  Scenario: Registering a custom ordering
+    Given a file named "register_custom_ordering_spec.rb" with:
+      """ruby
+      RSpec.configure do |rspec|
+        rspec.register_ordering(:reverse) do |items|
+          items.reverse
+        end
+      end
+
+      RSpec.describe "A group that must run in reverse order", :order => :reverse do
+        before(:context) { @list = [] }
+
+        it "passes when run second" do
+          @list << 2
+          expect(@list).to eq([1, 2])
+        end
+
+        it "passes when run first" do
+          @list << 1
+          expect(@list).to eq([1])
+        end
+      end
+      """
+    When I run `rspec register_custom_ordering_spec.rb`
+    Then the examples should all pass
+
+  Scenario: Using a custom global ordering
+    Given a file named "register_global_ordering_spec.rb" with:
+      """ruby
+      RSpec.configure do |rspec|
+        rspec.register_ordering(:global) do |items|
+          items.reverse
+        end
+      end
+
+      RSpec.describe "A group without :order metadata" do
+        before(:context) { @list = [] }
+
+        it "passes when run second" do
+          @list << 2
+          expect(@list).to eq([1, 2])
+        end
+
+        it "passes when run first" do
+          @list << 1
+          expect(@list).to eq([1])
+        end
+      end
+      """
+    When I run `rspec register_global_ordering_spec.rb`
+    Then the examples should all pass
+

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

@@ -0,0 +1,62 @@
+Feature: pattern
+
+  Use the `pattern` option to configure RSpec to look for specs in files that match
+  a pattern instead of the default `"**/*_spec.rb"`.
+
+  ```ruby
+  RSpec.configure { |c| c.pattern = '**/*.spec' }
+  ```
+
+  Rather than using `require 'spec_helper'` at the top of each spec file,
+  ensure that you have `--require spec_helper` in `.rspec`. That will always
+  load before the pattern is resolved. With the pattern thus configured,
+  only those spec files that match the pattern will then be loaded.
+
+  Background:
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      RSpec.describe "two specs" do
+        it "passes" do
+        end
+
+        it "passes too" do
+        end
+      end
+      """
+
+  Scenario: Override the default pattern in configuration
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure do |config|
+        config.pattern = '**/*.spec'
+      end
+      """
+    And a file named "spec/one_example.spec" with:
+      """ruby
+      RSpec.describe "something" do
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec -rspec_helper`
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: Append to the default pattern in configuration
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure do |config|
+        config.pattern << ',**/*.spec'
+      end
+      """
+    And a file named "spec/two_examples.spec" with:
+      """ruby
+      RSpec.describe "something" do
+        it "passes" do
+        end
+
+        it "passes again" do
+        end
+      end
+      """
+    When I run `rspec -rspec_helper`
+    Then the output should contain "4 examples, 0 failures"

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

@@ -0,0 +1,220 @@
+Feature: Profile examples
+
+  The `--profile` command line option (available from `RSpec.configure` as
+  `#profile_examples`), when set, will cause RSpec to dump out a list of your
+  slowest examples. By default, it prints the 10 slowest examples, but you can
+  set it to a different value to have it print more or fewer slow examples. If
+  `--fail-fast` option is used together with `--profile` and there is a failure,
+  slow examples are not shown.
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      """
+    And a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      RSpec.describe "something" do
+        it "sleeps for 0.1 seconds (example 1)" do
+          sleep 0.1
+          expect(1).to eq(1)
+        end
+
+        it "sleeps for 0 seconds (example 2)" do
+          expect(2).to eq(2)
+        end
+
+        it "sleeps for 0.15 seconds (example 3)" do
+          sleep 0.15
+          expect(3).to eq(3)
+        end
+
+        it "sleeps for 0.05 seconds (example 4)" do
+          sleep 0.05
+          expect(4).to eq(4)
+        end
+
+        it "sleeps for 0.05 seconds (example 5)" do
+          sleep 0.05
+          expect(5).to eq(5)
+        end
+
+        it "sleeps for 0.05 seconds (example 6)" do
+          sleep 0.05
+          expect(6).to eq(6)
+        end
+
+        it "sleeps for 0.05 seconds (example 7)" do
+          sleep 0.05
+          expect(7).to eq(7)
+        end
+
+        it "sleeps for 0.05 seconds (example 8)" do
+          sleep 0.05
+          expect(8).to eq(8)
+        end
+
+        it "sleeps for 0.05 seconds (example 9)" do
+          sleep 0.05
+          expect(9).to eq(9)
+        end
+
+        it "sleeps for 0.05 seconds (example 10)" do
+          sleep 0.05
+          expect(10).to eq(10)
+        end
+
+        it "sleeps for 0.05 seconds (example 11)" do
+          sleep 0.05
+          expect(11).to eq(11)
+        end
+      end
+      """
+
+  Scenario: By default does not show profile
+    When I run `rspec spec`
+    Then the examples should all pass
+    And the output should not contain "example 1"
+    And the output should not contain "example 2"
+    And the output should not contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: Setting `profile_examples` to true shows 10 examples
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.profile_examples = true }
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+    And the output should contain "Top 10 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should contain "example 4"
+    And the output should contain "example 5"
+    And the output should contain "example 6"
+    And the output should contain "example 7"
+    And the output should contain "example 8"
+    And the output should contain "example 9"
+    And the output should contain "example 10"
+    And the output should contain "example 11"
+
+  Scenario: Setting `profile_examples` to 2 shows 2 examples
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.profile_examples = 2 }
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+    And the output should contain "Top 2 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: Setting profile examples through CLI using `--profile`
+    When I run `rspec spec --profile 2`
+    Then the examples should all pass
+    And the output should contain "Top 2 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: Using `--no-profile` overrules config options
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.profile_examples = true }
+      """
+    When I run `rspec spec --no-profile`
+    Then the examples should all pass
+    And the output should not contain "example 1"
+    And the output should not contain "example 2"
+    And the output should not contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: Using `--profile` with `--fail-fast` shows slow examples if everything passes
+    When I run `rspec spec --fail-fast --profile`
+    Then the examples should all pass
+    And the output should contain "Top 10 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should contain "example 4"
+    And the output should contain "example 5"
+    And the output should contain "example 6"
+    And the output should contain "example 7"
+    And the output should contain "example 8"
+    And the output should contain "example 9"
+    And the output should contain "example 10"
+    And the output should contain "example 11"
+
+  Scenario: Using `--profile` shows slow examples even in case of failures
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      RSpec.describe "something" do
+        it "sleeps for 0.1 seconds (example 1)" do
+          sleep 0.1
+          expect(1).to eq(1)
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec --profile`
+    Then the output should contain "2 examples, 1 failure"
+    And the output should contain "Top 2 slowest examples"
+    And the output should contain "example 1"
+
+  Scenario: Using `--profile` with `--fail-fast` doesn't show slow examples in case of failures
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      RSpec.describe "something" do
+        it "sleeps for 0.1 seconds (example 1)" do
+          sleep 0.1
+          expect(1).to eq(1)
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+      """
+    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"