rspec-core 3.0.0.beta2 → 3.0.0.rc1

data/features/formatters/configurable_colors.feature

@@ -1,31 +0,0 @@
-Feature: Configurable colors
-
-  RSpec allows you to configure the terminal colors used in the text formatters.
-
-  * `failure_color`: Color used when tests fail (default: `:red`)
-  * `success_color`: Color used when tests pass (default: `:green`)
-  * `pending_color`: Color used when tests are pending (default: `:yellow`)
-  * `fixed_color`: Color used when a pending block inside an example passes, but was expected to fail (default: `:blue`)
-  * `detail_color`: Color used for miscellaneous test details (default: `:cyan`)
-
-  Colors are normally specified as symbols. Options are `:black`, `:red`,
-  `:green`, `:yellow`, `:blue`, `:magenta`, `:cyan`, and `:white`.
-
-  @ansi
-  Scenario: Customizing the failure color
-    Given a file named "custom_failure_color_spec.rb" with:
-      """ruby
-      RSpec.configure do |config|
-        config.failure_color = :magenta
-        config.tty = true
-        config.color = true
-      end
-
-      describe "failure" do
-        it "fails and uses the custom color" do
-          expect(2).to eq(4)
-        end
-      end
-      """
-      When I run `rspec custom_failure_color_spec.rb --format progress`
-      Then the failing example is printed in magenta

data/features/formatters/custom_formatter.feature

@@ -1,68 +0,0 @@
-Feature: custom formatters
-
-  RSpec ships with general purpose output formatters. You can tell RSpec which
-  one to use using the [`--format` command line
-  option]('../command_line/format_option').
-
-  When RSpec's built-in output formatters don't, however, give you everything
-  you need, you can write your own custom formatter and tell RSpec to use that
-  one instead.  The simplest way is to subclass RSpec's `BaseTextFormatter`,
-  and then override just the methods that you want to modify.
-
-  Scenario: custom formatter
-    Given a file named "custom_formatter.rb" with:
-      """ruby
-      require "rspec/core/formatters/base_text_formatter"
-
-      class CustomFormatter < RSpec::Core::Formatters::BaseTextFormatter
-
-        # This registers the notifications this formatter supports, and tells
-        # us that this was written against the RSpec 3.x formatter API.
-        RSpec::Core::Formatters.register self, :example_started
-
-        def initialize(output)
-          super(output)
-        end
-
-        def example_started(notification)
-          output << "example: " << notification.example.description
-        end
-      end
-      """
-    And a file named "example_spec.rb" with:
-      """ruby
-      describe "my group" do
-        specify "my example" do
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --require ./custom_formatter.rb --format CustomFormatter`
-    Then the output should contain "example: my example"
-    And  the exit status should be 0
-
-  Scenario: a legacy custom formatter
-    Given a file named "custom_formatter.rb" with:
-      """ruby
-      require "rspec/core/formatters/base_text_formatter"
-
-      class CustomFormatter < RSpec::Core::Formatters::BaseTextFormatter
-        def initialize(output)
-          super(output)
-        end
-
-        def example_started(proxy)
-          output << "example: " << proxy.description
-        end
-      end
-      """
-    And a file named "example_spec.rb" with:
-      """ruby
-      describe "my group" do
-        specify "my example" do
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --require ./custom_formatter.rb --format CustomFormatter`
-    Then the output should contain "example: my example"
-    And the output should contain "The CustomFormatter formatter uses the deprecated formatter interface."
-    And  the exit status should be 0

data/features/formatters/json_formatter.feature

@@ -1,30 +0,0 @@
-Feature: JSON formatter
-
-  Scenario: Formatting example names for retry
-    Given a file named "various_spec.rb" with:
-    """ruby
-    describe "Various" do
-      it "fails" do
-        expect("fail").to eq("succeed")
-      end
-
-      it "succeeds" do
-        expect("succeed").to eq("succeed")
-      end
-
-      it "pends"
-    end
-    """
-    When I run `rspec various_spec.rb --format j`
-    Then the output should contain all of these:
-          |"summary_line":"3 examples, 1 failure, 1 pending"|
-          |"examples":[                                     |
-          |"description":"fails"                             |
-          |"full_description":"Various fails"                |
-          |"status":"failed"                                 |
-          |"file_path":"./various_spec.rb"                   |
-          |"line_number":2                                   |
-          |"exception":{                                     |
-          |"class":"RSpec::Expectations::ExpectationNotMetError"|
-
-    And the exit status should be 1

data/features/formatters/regression_tests.feature

@@ -1,95 +0,0 @@
-Feature: Regression tests for legacy custom formatters
-
-  Background:
-    Given a file named ".rspec" with:
-      """
-      --require spec_helper
-      """
-      And a file named "spec/spec_helper.rb" with:
-      """
-      RSpec.configure do |rspec|
-        rspec.after(:suite) do
-          puts rspec.formatters.map(&:class).inspect
-        end
-      end
-      """
-      And a file named "spec/passing_and_failing_spec.rb" with:
-      """ruby
-      RSpec.describe "Some examples" do
-        it "passes" do
-          expect(1).to eq(1)
-        end
-
-        it "fails" do
-          expect(1).to eq(2)
-        end
-
-        context "nested" do
-          it "passes" do
-            expect(1).to eq(1)
-          end
-
-          it "fails" do
-            expect(1).to eq(2)
-          end
-        end
-      end
-      """
-      And a file named "spec/pending_spec.rb" with:
-      """ruby
-      RSpec.describe "Some pending examples" do
-        context "pending" do
-          it "is reported as pending" do
-            pending; expect(1).to eq(2)
-          end
-
-          it "is reported as failing" do
-            pending; expect(1).to eq(1)
-          end
-        end
-      end
-      """
-
-  Scenario: Use fuubar formatter
-    When I run `rspec --format Fuubar`
-    Then the output should contain "Progress: |============"
-     And the output should contain "6 examples, 3 failures, 1 pending"
-     And the output should contain "The Fuubar formatter uses the deprecated formatter interface"
-     But the output should not contain any error backtraces
-     And the output should not contain "ProgressFormatter"
-
-  Scenario: Use rspec-instafail formatter
-    When I run `rspec --format RSpec::Instafail`
-    Then the output should contain "6 examples, 3 failures, 1 pending"
-     And the output should contain "The RSpec::Instafail formatter uses the deprecated formatter interface"
-     But the output should not contain any error backtraces
-     And the output should not contain "ProgressFormatter"
-
-  Scenario: Use rspec-extra-formatters JUnit formatter
-    When I run `rspec --require rspec-extra-formatters --format JUnitFormatter`
-    Then the output should contain:
-      """
-      <testsuite errors="0" failures="3" skipped="1" tests="6"
-      """
-     And the output should contain "The JUnitFormatter formatter uses the deprecated formatter interface"
-     But the output should not contain any error backtraces
-     And the output should not contain "ProgressFormatter"
-
-  @wip @announce
-  Scenario: Use rspec-extra-formatters Tap formatter
-    When I run `rspec --require rspec-extra-formatters --format TapFormatter`
-    Then the output should contain "TAP version 13"
-     And the output should contain "The TapFormatter formatter uses the deprecated formatter interface"
-     But the output should not contain any error backtraces
-     And the output should not contain "ProgressFormatter"
-
-  @wip @announce
-  Scenario: Use rspec-spinner formatter
-    When I run `rspec --require rspec_spinner --format RspecSpinner::Spinner`
-    Then the output should contain "TBD"
-
-  @wip @announce
-  Scenario: Use nyancat formatter
-    When I run `rspec --format NyanCatFormatter`
-    Then the output should contain "TBD"
-

data/features/formatters/text_formatter.feature

@@ -1,46 +0,0 @@
-Feature: text formatter
-
-  In order to easily see the result of running my specs
-  As an RSpec user
-  I want clear, concise, well-formatted output
-
-  Scenario: Backtrace formatting for failing specs in multiple files
-    Given a file named "string_spec.rb" with:
-      """ruby
-      describe String do
-        it "has a failing example" do
-          expect("foo".reverse).to eq("ofo")
-        end
-      end
-      """
-    And a file named "integer_spec.rb" with:
-      """ruby
-      describe Integer do
-        it "has a failing example" do
-          expect(7 + 5).to eq(11)
-        end
-      end
-      """
-    When I run `rspec integer_spec.rb string_spec.rb`
-    Then the backtrace-normalized output should contain:
-      """
-        1) Integer has a failing example
-           Failure/Error: expect(7 + 5).to eq(11)
-             
-             expected: 11
-                  got: 12
-             
-             (compared using ==)
-           # ./integer_spec.rb:3
-      """
-    And the backtrace-normalized output should contain:
-      """
-        2) String has a failing example
-           Failure/Error: expect("foo".reverse).to eq("ofo")
-             
-             expected: "ofo"
-                  got: "oof"
-             
-             (compared using ==)
-           # ./string_spec.rb:3
-      """

data/features/helper_methods/arbitrary_methods.feature

@@ -1,40 +0,0 @@
-Feature: arbitrary helper methods
-
-  You can define methods in any example group using Ruby's `def` keyword or
-  `define_method` method. These _helper_ methods are exposed to examples in the
-  group in which they are defined and groups nested within that group, but not
-  parent or sibling groups.
-
-  Scenario: use a method defined in the same group
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe "an example" do
-        def help
-          :available
-        end
-
-        it "has access to methods defined in its group" do
-          expect(help).to be(:available)
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass
-
-  Scenario: use a method defined in a parent group
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe "an example" do
-        def help
-          :available
-        end
-
-        describe "in a nested group" do
-          it "has access to methods defined in its parent group" do
-            expect(help).to be(:available)
-          end
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass

data/features/helper_methods/let.feature

@@ -1,50 +0,0 @@
-Feature: let and let!
-
-  Use `let` to define a memoized helper method.  The value will be cached
-  across multiple calls in the same example but not across examples.
-
-  Note that `let` is lazy-evaluated: it is not evaluated until the first time
-  the method it defines is invoked. You can use `let!` to force the method's
-  invocation before each example.
-
-  Scenario: use let to define memoized helper method
-    Given a file named "let_spec.rb" with:
-      """ruby
-      $count = 0
-      describe "let" do
-        let(:count) { $count += 1 }
-
-        it "memoizes the value" do
-          expect(count).to eq(1)
-          expect(count).to eq(1)
-        end
-
-        it "is not cached across examples" do
-          expect(count).to eq(2)
-        end
-      end
-      """
-    When I run `rspec let_spec.rb`
-    Then the examples should all pass
-
-  Scenario: use let! to define a memoized helper method that is called in a before hook
-    Given a file named "let_bang_spec.rb" with:
-      """ruby
-      $count = 0
-      describe "let!" do
-        invocation_order = []
-
-        let!(:count) do
-          invocation_order << :let!
-          $count += 1
-        end
-
-        it "calls the helper method in a before hook" do
-          invocation_order << :example
-          expect(invocation_order).to eq([:let!, :example])
-          expect(count).to eq(1)
-        end
-      end
-      """
-    When I run `rspec let_bang_spec.rb`
-    Then the examples should all pass

data/features/helper_methods/modules.feature

@@ -1,146 +0,0 @@
-Feature: Define helper methods in a module
-
-  You can define helper methods in a module and include it in
-  your example groups using the `config.include` configuration
-  option.  `config.extend` can be used to extend the module onto
-  your example groups so that the methods in the module are available
-  in the example groups themselves (but not in the actual examples).
-
-  You can also include or extend the module onto only certain example
-  groups by passing a metadata hash as the last argument.  Only groups
-  that match the given metadata will include or extend the module. You
-  can also specify metadata using only symbols.
-
-  Background:
-    Given a file named "helpers.rb" with:
-      """ruby
-      module Helpers
-        def help
-          :available
-        end
-      end
-      """
-
-  Scenario: include a module in all example groups
-    Given a file named "include_module_spec.rb" with:
-      """ruby
-      require './helpers'
-
-      RSpec.configure do |c|
-        c.include Helpers
-      end
-
-      describe "an example group" do
-        it "has access to the helper methods defined in the module" do
-          expect(help).to be(:available)
-        end
-      end
-      """
-    When I run `rspec include_module_spec.rb`
-    Then the examples should all pass
-
-  Scenario: extend a module in all example groups
-    Given a file named "extend_module_spec.rb" with:
-      """ruby
-      require './helpers'
-
-      RSpec.configure do |c|
-        c.extend Helpers
-      end
-
-      describe "an example group" do
-        puts "Help is #{help}"
-
-        it "does not have access to the helper methods defined in the module" do
-          expect { help }.to raise_error(NameError)
-        end
-      end
-      """
-    When I run `rspec extend_module_spec.rb`
-    Then the examples should all pass
-    And the output should contain "Help is available"
-
-  Scenario: include a module in only some example groups
-    Given a file named "include_module_in_some_groups_spec.rb" with:
-      """ruby
-      require './helpers'
-
-      RSpec.configure do |c|
-        c.include Helpers, :foo => :bar
-      end
-
-      describe "an example group with matching metadata", :foo => :bar do
-        it "has access to the helper methods defined in the module" do
-          expect(help).to be(:available)
-        end
-      end
-
-      describe "an example group without matching metadata" do
-        it "does not have access to the helper methods defined in the module" do
-          expect { help }.to raise_error(NameError)
-        end
-      end
-      """
-    When I run `rspec include_module_in_some_groups_spec.rb`
-    Then the examples should all pass
-
-  Scenario: extend a module in only some example groups
-    Given a file named "extend_module_in_only_some_groups_spec.rb" with:
-      """ruby
-      require './helpers'
-
-      RSpec.configure do |c|
-        c.extend Helpers, :foo => :bar
-      end
-
-      describe "an example group with matching metadata", :foo => :bar do
-        puts "In a matching group, help is #{help}"
-
-        it "does not have access to the helper methods defined in the module" do
-          expect { help }.to raise_error(NameError)
-        end
-      end
-
-      describe "an example group without matching metadata" do
-        puts "In a non-matching group, help is #{help rescue 'not available'}"
-
-        it "does not have access to the helper methods defined in the module" do
-          expect { help }.to raise_error(NameError)
-        end
-      end
-      """
-    When I run `rspec extend_module_in_only_some_groups_spec.rb`
-    Then the examples should all pass
-    And the output should contain "In a matching group, help is available"
-    And the output should contain "In a non-matching group, help is not available"
-
-  Scenario: use symbols as metadata
-    Given a file named "symbols_as_metadata_spec.rb" with:
-      """ruby
-      require './helpers'
-
-      RSpec.configure do |c|
-        c.include Helpers, :include_helpers
-        c.extend  Helpers, :extend_helpers
-      end
-
-      describe "an example group with matching include metadata", :include_helpers do
-        puts "In a group not matching the extend filter, help is #{help rescue 'not available'}"
-
-        it "has access to the helper methods defined in the module" do
-          expect(help).to be(:available)
-        end
-      end
-
-      describe "an example group with matching extend metadata", :extend_helpers do
-        puts "In a group matching the extend filter, help is #{help}"
-
-        it "does not have access to the helper methods defined in the module" do
-          expect { help }.to raise_error(NameError)
-        end
-      end
-      """
-    When I run `rspec symbols_as_metadata_spec.rb`
-    Then the examples should all pass
-    And the output should contain "In a group not matching the extend filter, help is not available"
-    And the output should contain "In a group matching the extend filter, help is available"