rspec-core 3.0.0.beta2 → 3.0.0.rc1

data/features/configuration/order_and_seed.feature

@@ -1,3 +0,0 @@
-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 <a href='../command_line/order.feature'>the documentation on the --order command line option</a> for more on this.

data/features/configuration/output_stream.feature

@@ -1,24 +0,0 @@
-Feature: output_stream
-
-  Define a custom output stream (default `$stdout`).  Aliases: `:output`, `:out`.
-
-    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'
-      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/features/configuration/overriding_global_ordering.feature

@@ -1,93 +0,0 @@
-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
-      describe "examples only pass when they are run in order", :order => :defined do
-        before(:all) { @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
-
-      describe "A group that must run in reverse order", :order => :reverse do
-        before(:all) { @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
-
-      describe "A group without :order metadata" do
-        before(:all) { @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/features/configuration/pattern.feature

@@ -1,38 +0,0 @@
-Feature: pattern
-
-  Use the pattern option to tell RSpec to look for specs in files that match a pattern other than "**/*_spec.rb".
-
-  Background:
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "two specs here" do
-        it "passes" do
-        end
-
-        it "passes too" do
-        end
-      end
-      """
-    And a file named "spec/example_test.rb" with:
-      """ruby
-      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 "2 examples, 0 failures"
-
-  Scenario: the --pattern flag makes RSpec run files matching the specified pattern and ignore the default pattern
-   When I run `rspec -P "**/*_test.rb"`
-   Then the output should contain "1 example, 0 failures"
-
-  Scenario: the --pattern flag can be used to pass in multiple patterns, separated by comma
-   When I run `rspec -P "**/*_test.rb,**/*_spec.rb"`
-   Then the output should contain "3 examples, 0 failures"
-
-  Scenario: the --pattern flag accepts shell style glob unions
-   When I run `rspec -P "**/*_{test,spec}.rb"`
-   Then the output should contain "3 examples, 0 failures"

data/features/configuration/profile.feature

@@ -1,220 +0,0 @@
-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"
-
-      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
-    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"
-
-      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"
-
-      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"

data/features/configuration/read_options_from_file.feature

@@ -1,90 +0,0 @@
-Feature: read command line configuration options from files
-
-  RSpec reads command line configuration options from files in two different
-  locations:
-
-    Local: `./.rspec-local` (i.e. in the project's root directory, can be gitignored)
-    Project:  `./.rspec` (i.e. in the project's root directory, usually checked into the project)
-    Global: `~/.rspec` (i.e. in the user's home directory)
-
-  Configuration options are loaded from `~/.rspec`, `.rspec`,
-  `.rspec-local`, command line switches, and the `SPEC_OPTS` environment
-  variable (listed in lowest to highest precedence; for example, an option
-  in `~/.rspec` can be overridden by an option in `.rspec-local`).
-
-  Scenario: color set in .rspec
-    Given a file named ".rspec" with:
-      """
-      --color
-      """
-    And a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "color_enabled" do
-        context "when set with RSpec.configure" do
-          before do
-            # color is disabled for non-tty output, so stub the output stream
-            # to say it is tty, even though we're running this with cucumber
-            allow(RSpec.configuration.output_stream).to receive(:tty?) { true }
-          end
-
-          it "is true" do
-            expect(RSpec.configuration).to be_color_enabled
-          end
-        end
-      end
-      """
-    When I run `rspec ./spec/example_spec.rb`
-    Then the examples should all pass
-
-  Scenario: custom options file
-    Given a file named "my.options" with:
-      """
-      --format documentation
-      """
-    And a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "formatter set in custom options file" do
-        it "sets formatter" do
-          expect(RSpec.configuration.formatters.first).
-            to be_a(RSpec::Core::Formatters::DocumentationFormatter)
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb --options my.options`
-    Then the examples should all pass
-
-  Scenario: RSpec ignores ./.rspec when custom options file is used
-    Given a file named "my.options" with:
-      """
-      --format documentation
-      """
-    And a file named ".rspec" with:
-      """
-      --color
-      """
-    And a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "custom options file" do
-        it "causes .rspec to be ignored" do
-          expect(RSpec.configuration.color_enabled).to be_falsey
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb --options my.options`
-    Then the examples should all pass
-
-  Scenario: using ERB in .rspec
-    Given a file named ".rspec" with:
-      """
-      --format <%= true ? 'documentation' : 'progress' %>
-      """
-    And a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "formatter" do
-        it "is set to documentation" do
-          expect(RSpec.configuration.formatters.first).to be_an(RSpec::Core::Formatters::DocumentationFormatter)
-        end
-      end
-      """
-    When I run `rspec ./spec/example_spec.rb`
-    Then the examples should all pass