rspec-core 2.99.2 → 3.0.0.beta1

metadata.gz.sig

@@ -0,0 +1 @@
+ut�>X??�!�ԯ���h?u�n�� s������%a��sc��j(x��9b:9a�}��]�L�#mO>2��Z�lHs�AOi�dE�P��;K�����|6�h9/���2�5>fD�{��$�Zx߿�B~��j��g�|"ʙ��Z�!���������D=�'��F"�=r���ϋ�lK(�t�E0k�k_��P��.����Ѫ��.��W\l��9��wsP��RB�VN�ׯi�JW��j��9h�u�4R�8��5�-J�

data/exe/autospec

@@ -1,13 +0,0 @@
-#!/usr/bin/env ruby
-require 'rspec/core/deprecation'
-RSpec.warn_deprecation <<-WARNING
-************************************************************
-REMOVAL NOTICE: you are using behaviour that has been
-removed from rspec-2.
-
-* The 'autospec' command is no longer supported.
-* Please use 'autotest' instead.
-
-This message will be removed from a future version of rspec.
-************************************************************
-WARNING

data/features/Autotest.md

@@ -1,38 +0,0 @@
-RSpec ships with a specialized subclass of Autotest. To use it, just add a
-`.rspec` file to your project's root directory, and run the `autotest` command
-as normal:
-
-    $ autotest
-
-## Bundler
-
-The `autotest` command generates a shell command that runs your specs. If you
-are using Bundler, and you want the shell command to include `bundle exec`,
-require the Autotest bundler plugin in a `.autotest` file in the project's root
-directory or your home directory:
-
-    # in .autotest
-    require "autotest/bundler"
-
-## Upgrading from previous versions of rspec
-
-Previous versions of RSpec used a different mechanism for telling autotest to
-invoke RSpec's Autotest extension: it generated an `autotest/discover.rb` file
-in the project's root directory. This is no longer necessary with the new
-approach of RSpec looking for a `.rspec` file, so feel free to delete the
-`autotest/discover.rb` file in the project root if you have one.
-
-## Gotchas
-
-### Invalid Option: --tty
-
-The `--tty` option was [added in rspec-core-2.2.1](changelog), and is used
-internally by RSpec. If you see an error citing it as an invalid option, you'll
-probably see there are two or more versions of rspec-core in the backtrace: one
-< 2.2.1 and one >= 2.2.1.
-
-This usually happens because you have a newer rspec-core installed, and an
-older rspec-core specified in a Bundler Gemfile. If this is the case, you can:
-
-1. specify the newer version in the Gemfile (recommended)
-2. prefix the `autotest` command with `bundle exec`

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/subject/attribute_of_subject.feature

@@ -1,124 +0,0 @@
-Feature: attribute of subject
-
-  WARNING: `its` will be extracted from rspec-core-3.0 into its own gem.
-
-  Use the `its` method as a short-hand to generate a nested example group with
-  a single example that specifies the expected value of an attribute of the
-  subject.  This can be used with an implicit or explicit subject.
-
-  `its` accepts a symbol or a string, and a block representing the example.
-
-      its(:size)    { should eq(1) }
-      its("length") { should eq(1) }
-
-  You can use a string with dots to specify a nested attribute (i.e. an
-  attribute of the attribute of the subject).
-
-      its("phone_numbers.size") { should eq(2) }
-
-  When the subject is a hash, you can pass in an array with a single key to
-  access the value at that key in the hash.
-
-      its([:key]) { should eq(value) }
-
-  Scenario: specify value of an attribute
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Array do
-        context "when first created" do
-          its(:size) { should eq(0) }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --format documentation`
-    Then the output should contain:
-      """
-      Array
-        when first created
-          size
-            should eq 0
-      """
-
-  Scenario: specify value of a nested attribute
-    Given a file named "example_spec.rb" with:
-      """ruby
-      class Person
-        attr_reader :phone_numbers
-        def initialize
-          @phone_numbers = []
-        end
-      end
-
-      describe Person do
-        context "with one phone number (555-1212)"do
-          subject do
-            person = Person.new
-            person.phone_numbers << "555-1212"
-            person
-          end
-
-          its("phone_numbers.first") { should eq("555-1212") }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --format documentation`
-    Then the output should contain:
-      """
-      Person
-        with one phone number (555-1212)
-          phone_numbers.first
-            should eq "555-1212"
-      """
-
-  Scenario: specify value of an attribute of a hash
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Hash do
-        context "with two items" do
-          subject do
-            {:one => 'one', :two => 'two'}
-          end
-
-          its(:size) { should eq(2) }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass
-
-  Scenario: specify value for key in a hash
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Hash do
-        context "with keys :one and 'two'" do
-          subject do
-            {:one => 1, "two" => 2}
-          end
-
-          its([:one]) { should eq(1) }
-          its(["two"]) { should eq(2) }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass
-
-  Scenario: specify value for key in a hash-like object
-    Given a file named "example_spec.rb" with:
-      """ruby
-      require 'matrix'
-
-      describe Matrix do
-        context "with values [[1, 2], [3, 4]]" do
-          subject do
-            Matrix[[1, 2], [3, 4]]
-          end
-
-          its([0, 1]) { should eq(2) }
-          its([1, 0]) { should eq(3) }
-          its([1, 2]) { should be_nil }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb`
-    Then the examples should all pass

data/features/subject/one_liner_syntax.feature

@@ -1,71 +0,0 @@
-Feature: One-liner syntax
-
-  RSpec supports a one-liner syntax for setting an expectation
-  on the `subject`. RSpec will give the examples a doc string
-  that is auto-generated from the matcher used in the example.
-  This is designed specifically to help avoid duplication in
-  situations where the doc string and the matcher used in the
-  example mirror each other exactly. When used excessively,
-  it can produce documentation output that does not read well
-  or contribute to understanding the object you are describing.
-
-  This comes in two flavors:
-
-    * `is_expected` is defined simply as `expect(subject)` and is
-      designed for when you are using rspec-expectations with its
-      newer expect-based syntax.
-    * `should` was designed back when rspec-expectations only had
-      a should-based syntax. However, it continues to be available
-      and work even if the `:should` syntax is disabled (since that
-      merely removes `Object#should` but this is
-      `RSpec::Core::ExampleGroup#should`).
-
-  Note: this feature is only available when using rspec-expectations.
-
-  Scenario: implicit subject
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Array do
-        describe "when first created" do
-          # Rather than:
-          # it "should be empty" do
-          #   subject.should be_empty
-          # end
-
-          it { should be_empty }
-          # or
-          it { is_expected.to be_empty }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --format doc`
-    Then the examples should all pass
-     And the output should contain:
-       """
-       Array
-         when first created
-           should be empty
-           should be empty
-       """
-
-  Scenario: explicit subject
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Array do
-        describe "with 3 items" do
-          subject { [1,2,3] }
-          it { should_not be_empty }
-          # or
-          it { is_expected.not_to be_empty }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --format doc`
-    Then the examples should all pass
-     And the output should contain:
-       """
-       Array
-         with 3 items
-           should not be empty
-           should not be empty
-       """

data/lib/autotest/discover.rb

@@ -1,10 +0,0 @@
-begin
-  # try to load rspec/autotest so we can check if the constant is defined below.
-  require 'rspec/autotest'
-rescue LoadError
-  # ignore. We print a deprecation warning later.
-end
-
-if File.exist?("./.rspec") && !defined?(::RSpec::Autotest)
-  Autotest.add_discovery { "rspec2" }
-end

data/lib/autotest/rspec2.rb

@@ -1,77 +0,0 @@
-begin
-  require 'rspec/autotest'
-rescue LoadError
-  require 'autotest'
-
-  # Derived from the `Autotest` class, extends the `autotest` command to work
-  # with RSpec.
-  #
-  # @note this will be extracted to a separate gem when we release rspec-3.
-  class Autotest::Rspec2 < Autotest
-
-    RSPEC_EXECUTABLE = File.expand_path('../../../exe/rspec', __FILE__)
-
-    def initialize
-      super()
-      clear_mappings
-      setup_rspec_project_mappings
-
-      # Example for Ruby 1.8: http://rubular.com/r/AOXNVDrZpx
-      # Example for Ruby 1.9: http://rubular.com/r/85ag5AZ2jP
-      self.failed_results_re = /^\s*\d+\).*\n\s+(?:\e\[\d*m)?Failure.*(\n(?:\e\[\d*m)?\s+#\s(.*)?:\d+(?::.*)?(?:\e\[\d*m)?)+$/m
-      self.completed_re = /\n(?:\e\[\d*m)?\d* examples?/m
-    end
-
-    # Adds conventional spec-to-file mappings to Autotest configuation.
-    def setup_rspec_project_mappings
-      add_mapping(%r%^spec/.*_spec\.rb$%) { |filename, _|
-        filename
-      }
-      add_mapping(%r%^lib/(.*)\.rb$%) { |_, m|
-        ["spec/#{m[1]}_spec.rb"]
-      }
-      add_mapping(%r%^spec/(spec_helper|shared/.*)\.rb$%) {
-        files_matching %r%^spec/.*_spec\.rb$%
-      }
-    end
-
-    # Overrides Autotest's implementation to read rspec output
-    def consolidate_failures(failed)
-      filters = new_hash_of_arrays
-      failed.each do |spec, trace|
-        if trace =~ /(.*spec\.rb)/
-          filters[$1] << spec
-        end
-      end
-      return filters
-    end
-
-    # Overrides Autotest's implementation to generate the rspec command to run
-    def make_test_cmd(files_to_test)
-      files_to_test.empty? ? '' :
-        %|#{prefix}"#{ruby}"#{suffix} -S "#{RSPEC_EXECUTABLE}" --tty #{normalize(files_to_test).keys.flatten.map { |f| %|"#{f}"|}.join(' ')}|
-    end
-
-    # Generates a map of filenames to Arrays for Autotest
-    def normalize(files_to_test)
-      files_to_test.keys.inject({}) do |result, filename|
-        result.merge!(File.expand_path(filename) => [])
-      end
-    end
-
-    private
-
-    def suffix
-      using_bundler? ? "" : defined?(:Gem) ? " -rrubygems" : ""
-    end
-
-    def using_bundler?
-      prefix =~ /bundle exec/
-    end
-
-    def gemfile?
-      File.exist?('./Gemfile')
-    end
-  end
-  Autotest.add_hook(:ran_command) { warn "\n\e[31mrspec-core's built in autotest support is deprecated and will be removed in RSpec 3. Please switch to the rspec-autotest gem.\e[0m" }
-end

data/lib/rspec/core/backtrace_cleaner.rb

@@ -1,46 +0,0 @@
-module RSpec
-  module Core
-    class BacktraceCleaner
-
-      DEFAULT_EXCLUSION_PATTERNS = [
-        /\/lib\d*\/ruby\//,
-        /org\/jruby\//,
-        /bin\//,
-        %r|/gems/|,
-        /spec\/spec_helper\.rb/,
-        /lib\/rspec\/(core|expectations|matchers|mocks)/
-      ]
-
-      attr_accessor :inclusion_patterns
-      attr_accessor :exclusion_patterns
-
-      def initialize(inclusion_patterns=nil, exclusion_patterns=DEFAULT_EXCLUSION_PATTERNS.dup)
-        @exclusion_patterns = exclusion_patterns
-
-        if inclusion_patterns.nil?
-          @inclusion_patterns = (matches_an_exclusion_pattern? Dir.getwd) ? [Regexp.new(Dir.getwd)] : []
-        else
-          @inclusion_patterns = inclusion_patterns
-        end
-      end
-
-      def exclude?(line)
-        @inclusion_patterns.none? {|p| line =~ p} and matches_an_exclusion_pattern?(line)
-      end
-
-      def full_backtrace=(true_or_false)
-        @exclusion_patterns = true_or_false ? [] : DEFAULT_EXCLUSION_PATTERNS.dup
-      end
-
-      def full_backtrace?
-        @exclusion_patterns.empty?
-      end
-
-      private
-
-      def matches_an_exclusion_pattern?(line)
-        @exclusion_patterns.any? {|p| line =~ p}
-      end
-    end
-  end
-end

data/lib/rspec/core/backward_compatibility.rb

@@ -1,55 +0,0 @@
-module RSpec
-  module Core
-    # @private
-    module ConstMissing
-      # Used to print deprecation warnings for Rspec and Spec constants (use
-      # RSpec instead)
-      def const_missing(name)
-        case name
-        when :Rspec, :Spec
-          RSpec.deprecate(name.to_s, :replacement => "RSpec")
-          RSpec
-        else
-          begin
-            super
-          rescue Exception => e
-            e.backtrace.reject! {|l| l =~ Regexp.compile(__FILE__) }
-            raise e
-          end
-        end
-      end
-    end
-  end
-
-  module Runner
-    # @deprecated use RSpec.configure instead.
-    def self.configure(&block)
-      RSpec.deprecate("Spec::Runner.configure", :replacement => "RSpec.configure")
-      RSpec.configure(&block)
-    end
-  end
-
-  # @private
-  module Rake
-    # Used to print deprecation warnings for Rake::SpecTask constant (use
-    # RSpec::Core::RakeTask instead)
-    def self.const_missing(name)
-      case name
-      when :SpecTask
-        RSpec.deprecate("Spec::Rake::SpecTask", :replacement => "RSpec::Core::RakeTask")
-        require 'rspec/core/rake_task'
-        RSpec::Core::RakeTask
-      else
-        begin
-          super
-        rescue Exception => e
-          e.backtrace.reject! {|l| l =~ Regexp.compile(__FILE__) }
-          raise e
-        end
-      end
-    end
-
-  end
-end
-
-Object.extend(RSpec::Core::ConstMissing)