rspec-core 2.99.0 → 3.0.0

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" 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
-            RSpec.configuration.output_stream.stub(:tty?) { true }
-          end
-
-          it "is true" do
-            RSpec.configuration.should 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
-          RSpec.configuration.formatters.first.
-            should 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
-          RSpec.configuration.color.should 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
-          RSpec.configuration.formatters.first.should be_an(RSpec::Core::Formatters::DocumentationFormatter)
-        end
-      end
-      """
-    When I run `rspec ./spec/example_spec.rb`
-    Then the examples should all pass

data/features/configuration/run_all_when_everything_filtered.feature

@@ -1,76 +0,0 @@
-Feature: run all when everything filtered
-
-  Use the run_all_when_everything_filtered option to tell RSpec to run all the
-  specs in the case where you try to run a filtered list of specs but no specs
-  match that filter. This works well when paired with an inclusion filter like
-  `:focus => true`, as it will run all the examples when none match the
-  inclusion filter.
-
-    RSpec.configure { |c| c.run_all_when_everything_filtered = true }
-
-  Background:
-    Given a file named "spec/spec_helper.rb" with:
-      """ruby
-      RSpec.configure {|c| c.run_all_when_everything_filtered = true}
-      """
-
-  Scenario: by default, no specs are run if they are all filtered out by an inclusion tag
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "examples" do
-        it "with no tag" do
-        end
-
-        it "with no tag as well" do
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb --tag some_tag`
-    Then the output should contain "0 examples, 0 failures"
-
-  Scenario: specs are still run if they are filtered out by an exclusion tag
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "examples" do
-        it "with no tag" do
-        end
-
-        it "with no tag as well" do
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb --tag ~some_tag`
-    Then the output should contain "2 examples, 0 failures"
-
-  Scenario: when the run_all_when_everything_filtered option is turned on, if there are any matches for the filtering tag, only those features are run
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      require "spec_helper"
-      describe "examples" do
-        it "with no tag", :some_tag => true do
-        end
-
-        it "with no tag as well" do
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb --tag some_tag`
-    Then the output should contain "1 example, 0 failures"
-    And the output should contain "Run options: include {:some_tag=>true}"
-
-  Scenario: when the run_all_when_everything_filtered option is turned on, all the specs are run when the tag has no matches
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      require "spec_helper"
-      describe "examples" do
-        it "with no tag" do
-        end
-
-        it "with no tag as well" do
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb --tag some_tag`
-    Then the output should contain "2 examples, 0 failures"
-    And the output should contain "All examples were filtered out; ignoring {:some_tag=>true}"
-

data/features/configuration/show_failures_in_pending_blocks.feature

@@ -1,61 +0,0 @@
-Feature: show_failures_in_pending_blocks
-
-  Use the show_failures_in_pending_blocks option to run the code in pending blocks while keeping the tests pending.
-
-    RSpec.configure { |c| c.show_failures_in_pending_blocks = true }
-
-  Background:
-    Given a file named "spec/spec_helper.rb" with:
-      """ruby
-      RSpec.configure {|c| c.show_failures_in_pending_blocks = true}
-      """
-
-  Scenario: by default, code in pending examples is not exercised
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "fails" do
-        pending "code will not be exercised" do
-          fail
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb`
-    Then the output should not contain "Failure/Error: pending { fail }"
-
-  Scenario: by default, code in pending blocks inside examples is not exercised
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "fails" do
-        it "code will not be exercised" do
-          pending { fail }
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb`
-    Then the output should not contain "Failure/Error: pending { fail }"
-
-  Scenario: when turned on, pending code blocks inside examples are exercised
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      require "spec_helper"
-      describe "fails" do
-        it "code will be exercised" do
-          pending { fail }
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb`
-    Then the output should contain "Failure/Error: pending { fail }"
-
-  Scenario: when turned on, code inside pending examples is not exercised
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      require "spec_helper"
-      describe "fails" do
-        pending "code will not be exercised" do
-          fail
-        end
-      end
-      """
-    When I run `rspec spec/example_spec.rb`
-    Then the output should not contain "Failure/Error: pending { fail }"

data/features/configuration/treat_symbols_as_metadata_keys_with_true_values.feature

@@ -1,52 +0,0 @@
-Feature: treat symbols as metadata keys with true values
-
-  Use the treat_symbols_as_metadata_keys_with_true_values option to tell RSpec that :key is shorthand for :key => true.
-
-    RSpec.configure { |c| c.treat_symbols_as_metadata_keys_with_true_values = true }
-
-  Background:
-    Given a file named "spec/spec_helper.rb" with:
-      """ruby
-      RSpec.configure { |c| c.treat_symbols_as_metadata_keys_with_true_values = true }
-      """
-
-  Scenario: by default, symbols without values are ignored and the specs are filtered out
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      describe "failed filtering" do
-        it "this will be filted out", :some_tag do
-          true
-        end
-
-        it "so will this" do
-          false
-        end
-      end
-      """
-      When I run `rspec spec/example_spec.rb --tag some_tag`
-      Then the output should contain "0 examples, 0 failures"
-      And the output should contain "All examples were filtered out"
-
-  Scenario: when treat_symbols_as_metadata_keys_with_true_values is true, specs can be tagged with only a symbol
-    Given a file named "spec/example_spec.rb" with:
-      """ruby
-      require "spec_helper"
-      describe "run me", :some_tag do
-        it "runs" do
-          true
-        end
-      end
-
-      describe "run one of these" do
-        it "run this one", :some_tag do
-          true
-        end
-
-        it "but not me" do
-          false
-        end
-      end
-      """
-      When I run `rspec spec/example_spec.rb --tag some_tag`
-      Then the output should contain "2 examples, 0 failures"
-      And the output should contain "Run options: include {:some_tag=>true}"

data/features/example_groups/basic_structure.feature

@@ -1,55 +0,0 @@
-Feature: basic structure (describe/it)
-
-  RSpec is a DSL for creating executable examples of how code is expected to
-  behave, organized in groups. It uses the words "describe" and "it" so we can
-  express concepts like a conversation:
-
-      "Describe an account when it is first opened."
-      "It has a balance of zero."
-
-  The `describe` method creates an example group.  Within the block passed to
-  `describe` you can declare nested groups using the `describe` or `context`
-  methods, or you can declare examples using the `it` or `specify` methods.
-
-  Under the hood, an example group is a class in which the block passed to
-  `describe` or `context` is evaluated. The blocks passed to `it` are evaluated
-  in the context of an _instance_ of that class.
-
-  Scenario: one group, one example
-    Given a file named "sample_spec.rb" with:
-    """ruby
-    describe "something" do
-      it "does something" do
-      end
-    end
-    """
-    When I run `rspec sample_spec.rb -f doc`
-    Then the output should contain:
-      """
-      something
-        does something
-      """
-
-  Scenario: nested example groups (using context)
-    Given a file named "nested_example_groups_spec.rb" with:
-    """ruby
-    describe "something" do
-      context "in one context" do
-        it "does one thing" do
-        end
-      end
-      context "in another context" do
-        it "does another thing" do
-        end
-      end
-    end
-    """
-    When I run `rspec nested_example_groups_spec.rb -fdoc`
-    Then the output should contain:
-      """
-      something
-        in one context
-          does one thing
-        in another context
-          does another thing
-      """

data/features/example_groups/shared_context.feature

@@ -1,74 +0,0 @@
-Feature: shared context
-
-  Use `shared_context` to define a block that will be evaluated in the context
-  of example groups either explicitly, using `include_context`, or implicitly by
-  matching metadata.
-
-  Background:
-    Given a file named "shared_stuff.rb" with:
-      """ruby
-      shared_context "shared stuff", :a => :b do
-        before { @some_var = :some_value }
-        def shared_method
-          "it works"
-        end
-        let(:shared_let) { {'arbitrary' => 'object'} }
-        subject do
-          'this is the subject'
-        end
-      end
-      """
-
-  Scenario: declare shared context and include it with include_context
-    Given a file named "shared_context_example.rb" with:
-      """ruby
-      require "./shared_stuff.rb"
-
-      describe "group that includes a shared context using 'include_context'" do
-        include_context "shared stuff"
-
-        it "has access to methods defined in shared context" do
-          shared_method.should eq("it works")
-        end
-
-        it "has access to methods defined with let in shared context" do
-          shared_let['arbitrary'].should eq('object')
-        end
-
-        it "runs the before hooks defined in the shared context" do
-          @some_var.should be(:some_value)
-        end
-
-        it "accesses the subject defined in the shared context" do
-          subject.should eq('this is the subject')
-        end
-      end
-      """
-    When I run `rspec shared_context_example.rb`
-    Then the examples should all pass
-
-  Scenario: declare shared context and include it with metadata
-    Given a file named "shared_context_example.rb" with:
-      """ruby
-      require "./shared_stuff.rb"
-
-      describe "group that includes a shared context using metadata", :a => :b do
-        it "has access to methods defined in shared context" do
-          shared_method.should eq("it works")
-        end
-
-        it "has access to methods defined with let in shared context" do
-          shared_let['arbitrary'].should eq('object')
-        end
-
-        it "runs the before hooks defined in the shared context" do
-          @some_var.should be(:some_value)
-        end
-
-        it "accesses the subject defined in the shared context" do
-          subject.should eq('this is the subject')
-        end
-      end
-      """
-    When I run `rspec shared_context_example.rb`
-    Then the examples should all pass