rspec-core 2.11.1 → 3.11.0

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' insted.
-
-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/README.md

@@ -1,17 +0,0 @@
-rspec-core provides the structure for RSpec code examples:
-
-    describe Account do
-      it "has a balance of zero when first opened" do
-        # example code goes here - for more on the 
-        # code inside the examples, see rspec-expectations 
-        # and rspec-mocks
-      end
-    end
-
-## Issues
-
-This documentation is [open
-source](https://github.com/rspec/rspec-core/tree/master/features), and a work
-in progress.  If you find it incomplete or confusing, please [submit an
-issue](http://github.com/rspec/rspec-core/issues), or, better yet, [a pull
-request](http://github.com/rspec/rspec-core).

data/features/Upgrade.md

@@ -1,364 +0,0 @@
-The [Changelog](changelog) has a complete list of everything that changed, but
-here are more detailed explanations for those items that warrant them.
-
-# rspec-core-2.7.0.rc1
-
-## what's new
-
-### `rspec` command with no arguments
-
-Now you can just type
-
-    rspec
-
-to run all the specs in the `spec` directory.  If you keep your specs in a
-different directory, you can override the default with the `--default_path`
-argument in a config file:
-
-    # in .rspec
-    --default_path specs
-
-### `rspec` command supports multiple line numbers
-
-Use either of the following to run the examples declared on lines
-37 and 42 of `a_spec.rb`:
-
-    rspec path/to/a_spec.rb --line_number 37 --line_number 42
-    rspec path/to/a_spec.rb:37:42
-
-## what's changed
-
-### `skip_bundler` and `gemfile` rake task options are deprecated and have no effect.
-
-RSpec's rake task invokes the `rspec` command in a subshell. If you invoke
-`bundle exec rake` or include `Bundler.setup` in your `Rakefile`, then
-Bundler will be activated in the subshell as well.
-
-Previously, the rake task managed this for you based on the presence of a
-`Gemfile`. In 2.7.0.rc1, this is done based on the presence of the
-`BUNDLE_GEMFILE` environment variable, which is set in the parent shell by Bundler.
-
-In 2.7.0.rc2 (not yet released), the rake task doesn't do anything at all.
-Turns out Bundler just does the right thing, so rspec doesn't need to do
-anything.
-
-# rspec-core-2.6
-
-## new APIs for sharing content
-
-Use `shared_context` together with `include_context` to share before/after
-hooks, let declarations, and method definitions across example groups.
-
-Use `shared_examples` together with `include_examples` to share examples
-across different contexts.
-
-All of the old APIs are still supported, but these 4 are easy to remember, and
-serve most use cases.
-
-See `shared_context` and `shared_examples` under "Example Groups" for more
-information.
-
-## `treat_symbols_as_metadata_keys_with_true_values`
-
-Yes it's a long name, but it's a great feature, and it's going to be the
-default behavior in rspec-3. This lets you add metadata to a group or example
-like this:
-
-    describe "something", :awesome do
-      ...
-
-And then you can run that group (or example) using the tags feature:
-
-    rspec spec --tag awesome
-
-We're making this an opt-in for rspec-2.6 because `describe "string", :symbol`
-is a perfectly legal construct in pre-2.6 releases and we want to maintain
-compatibility in minor releases as much as is possible.
-
-# rspec-core-2.3
-
-## `config.expect_with`
-
-Use this to configure RSpec to use rspec/expectations (default),
-stdlib assertions (Test::Unit with Ruby 1.8, MiniTest with Ruby 1.9),
-or both:
-
-    RSpec.configure do |config|
-      config.expect_with :rspec          # => rspec/expectations
-      config.expect_with :stdlib         # => Test::Unit or MinitTest
-      config.expect_with :rspec, :stdlib # => both
-    end
-
-# rspec-core-2.1
-
-## Command line
-
-### `--tags`
-
-Now you can tag groups and examples using metadata and access those tags from
-the command line. So if you have a group with `:foo => true`:
-
-    describe "something", :foo => true do
-      it "does something" do
-        # ...
-      end
-    end
-
-... now you can run just that group like this:
-
-    rspec spec --tags foo
-
-### `--fail-fast`
-
-Add this flag to the command line to tell rspec to clean up and exit after the
-first failure:
-
-    rspec spec --fail-fast
-
-## Metata/filtering
-
-### :if and :unless keys
-
-Use :if and :unless keys to conditionally run examples with simple boolean
-expressions:
-
-    describe "something" do
-      it "does something", :if => RUBY_VERSION == 1.8.6 do
-        # ...
-      end
-      it "does something", :unless => RUBY_VERSION == 1.8.6 do
-        # ...
-      end
-    end
-
-## Conditionally 'pending' examples
-
-Make examples pending based on a condition.  This is most useful when you
-have an example that runs in multiple contexts and fails in one of those due to
-a bug in a third-party dependency that you expect to be fixed in the future.
-
-    describe "something" do
-      it "does something that doesn't yet work right on JRuby" do
-        pending("waiting for the JRuby team to fix issue XYZ", :if => RUBY_PLATFORM == 'java') do
-          # the content of your spec
-        end
-      end
-    end
-
-This example would run normally on all ruby interpretters except JRuby.  On JRuby,
-it uses the block form of `pending`, which causes the example to still be run and
-will remain pending as long as it fails.  In the future, if you upgraded your
-JRuby installation to a newer release that allows the example to pass, RSpec
-will report it as a failure (`Expected pending '...' to fail.  No Error was raised.`),
-so that know that you can remove the call to `pending`.
-
-# New features in rspec-core-2.0
-
-### Runner
-
-The new runner for rspec-2 comes from Micronaut.
-
-### Metadata!
-
-In rspec-2, every example and example group comes with metadata information
-like the file and line number on which it was declared, the arguments passed to
-`describe` and `it`, etc.  This metadata can be appended to through a hash
-argument passed to `describe` or `it`, allowing us to pre and post-process
-each example in a variety of ways.
-
-### Filtering
-
-The most obvious use is for filtering the run. For example:
-
-    # in spec/spec_helper.rb
-    RSpec.configure do |c|
-      c.filter_run :focus => true
-    end
-
-    # in any spec file
-    describe "something" do
-      it "does something", :focus => true do
-        # ....
-      end
-    end
-
-When you run the `rspec` command, rspec will run only the examples that have
-`:focus => true` in the hash.
-
-You can also add `run_all_when_everything_filtered` to the config:
-
-    RSpec.configure do |c|
-      c.filter_run :focus => true
-      c.run_all_when_everything_filtered = true
-    end
-
-Now if there are no examples tagged with `:focus => true`, all examples
-will be run. This makes it really easy to focus on one example for a
-while, but then go back to running all of the examples by removing that
-argument from `it`. Works with `describe` too, in which case it runs
-all of the examples in that group.
-
-The configuration will accept a lambda, which provides a lot of flexibility
-in filtering examples. Say, for example, you have a spec for functionality that
-behaves slightly differently in Ruby 1.8 and Ruby 1.9. We have that in
-rspec-core, and here's how we're getting the right stuff to run under the
-right version:
-
-    # in spec/spec_helper.rb
-    RSpec.configure do |c|
-      c.exclusion_filter = { :ruby => lambda {|version|
-        !(RUBY_VERSION.to_s =~ /^#{version.to_s}/)
-      }}
-    end
-
-    # in any spec file
-    describe "something" do
-      it "does something", :ruby => 1.8 do
-        # ....
-      end
-
-      it "does something", :ruby => 1.9 do
-        # ....
-      end
-    end
-
-In this case, we're using `exclusion_filter` instead of `filter_run` or
-`filter`, which indicate _inclusion_ filters. So each of those examples is
-excluded if we're _not_ running the version of Ruby they work with.
-
-### Shared example groups
-
-Shared example groups are now run in a nested group within the including group
-(they used to be run in the same group). Nested groups inherit `before`, `after`,
-`around`, and `let` hooks, as well as any methods that are defined in the parent
-group.
-
-This new approach provides better encapsulation, better output, and an
-opportunity to add contextual information to the shared group via a block
-passed to `it_should_behave_like`.
-
-See [features/example\_groups/shared\_example\_group.feature](http://github.com/rspec/rspec-core/blob/master/features/example_groups/shared_example_group.feature) for more information.
-
-NOTICE: The including example groups no longer have access to any of the
-methods, hooks, or state defined inside a shared group. This will break rspec-1
-specs that were using shared example groups to extend the behavior of including
-groups.
-
-# Upgrading from rspec-1.x
-
-### rspec command
-
-The command to run specs is now `rspec` instead of `spec`.
-
-    rspec ./spec
-
-#### Co-habitation of rspec-1 and rspec-2
-
-Early beta versions of RSpec-2 included a `spec` command, which conflicted with
-the RSpec-1 `spec` command because RSpec-1's was installed by the rspec gem,
-while RSpec-2's is installed by the rspec-core gem.
-
-If you installed one of these early versions, the safest bet is to uninstall
-rspec-1 and rspec-core-2, and then reinstall both. After you do this, you will
-be able to run rspec-2 like this:
-
-    rspec ./spec
-
-... and rspec-1 like this:
-
-    spec _1.3.1_ ./spec
-
-Rubygems inspects the first argument to any gem executable to see if it's
-formatted like a version number surrounded by underscores. If so, it uses that
-version (e.g.  `1.3.1`). If not, it uses the most recent version (e.g.
-`2.0.0`).
-
-### rake task
-
-A few things changed in the Rake task used to run specs:
-
-1.  The file in which it is defined changed from `spec/rake/spectask` to
-    `rspec/core/rake_task`
-
-2.  The `spec_opts` accessor has been deprecated in favor of `rspec_opts`. Also,
-    the `rspec` command no longer supports the `--options` command line option
-    so the options must be embedded directly in the Rakefile, or stored in the
-    `.rspec` files mentioned above.
-
-3.  In RSpec-1, the rake task would read in rcov options from an `rcov.opts`
-    file. This is ignored by RSpec-2. RCov options are now set directly on the Rake
-    task:
-
-        RSpec::Core::RakeTask.new(:rcov) do |t|
-          t.rcov_opts =  %q[--exclude "spec"]
-        end
-
-3.  The `spec_files` accessor has been replaced by `pattern`.
-
-        # rspec-1
-        require 'spec/rake/spectask'
-
-        Spec::Rake::SpecTask.new do |t|
-          t.spec_opts = ['--options', "\"spec/spec.opts\""]
-          t.spec_files = FileList['spec/**/*.rb']
-        end
-
-        # rspec-2
-        require 'rspec/core/rake_task'
-
-        RSpec::Core::RakeTask.new do |t|
-          t.rspec_opts = ["-c", "-f progress", "-r ./spec/spec_helper.rb"]
-          t.pattern = 'spec/**/*_spec.rb'
-        end
-
-### autotest
-
-`autospec` is dead. Long live `autotest`.
-
-### RSpec is the new Spec
-
-The root namespace (top level module) is now `RSpec` instead of `Spec`, and
-the root directory under `lib` within all of the `rspec` gems is `rspec` instead of `spec`.
-
-### Configuration
-
-Typically in `spec/spec_helper.rb`, configuration is now done like this:
-
-    RSpec.configure do |c|
-      # ....
-    end
-
-### .rspec
-
-Command line options can be persisted in a `.rspec` file in a project. You
-can also store a `.rspec` file in your home directory (`~/.rspec`) with global
-options. Precedence is:
-
-    command line
-    ./.rspec
-    ~/.rspec
-
-### `context` is no longer a top-level method
-
-We removed `context` from the main object because it was creating conflicts with
-IRB and some users who had `Context` domain objects. `describe` is still there,
-so if you want to use `context` at the top level, just alias it:
-
-    alias :context :describe
-
-Of course, you can still use `context` to declare a nested group:
-
-    describe "something" do
-      context "in some context" do
-        it "does something" do
-          # ...
-        end
-      end
-    end
-
-### `$KCODE` no longer set implicitly to `'u'`
-
-In RSpec-1, the runner set `$KCODE` to `'u'`, which impacts, among other
-things, the behaviour of Regular Expressions when applied to non-ascii
-characters. This is no longer the case in RSpec-2.
-

data/features/command_line/README.md

@@ -1,28 +0,0 @@
-The `rspec` command comes with several options you can use to customize RSpec's
-behavior, including output formats, filtering examples, etc.
-
-For a full list of options, run the `rspec` command with the `--help` flag:
-
-    $ rspec --help
-
-### Run with `ruby`
-
-Generally, life is simpler if you just use the `rspec` command. If you must use the `ruby`
-command, however, you'll want to do the following:
-
-* `require 'rspec/autorun'`
-
-This tells RSpec to run your examples.  Do this in any file that you are
-passing to the `ruby` command.
-
-* Update the `LOAD_PATH`
-
-It is conventional to put configuration in and require assorted support files
-from `spec/spec_helper.rb`. It is also conventional to require that file from
-the spec files using `require 'spec_helper'`. This works because RSpec
-implicitly adds the `spec` directory to the `LOAD_PATH`. It also adds `lib`, so
-your implementation files will be on the `LOAD_PATH` as well.
-
-If you're using the `ruby` command, you'll need to do this yourself:
-
-    ruby -Ilib -Ispec path/to/spec.rb

data/features/command_line/example_name_option.feature

@@ -1,101 +0,0 @@
-Feature: --example option
-
-  Use the --example (or -e) option to filter examples by name.
-
-  The argument is compiled to a Ruby Regexp, and matched against the full
-  description of the example, which is the concatenation of descriptions of the
-  group (including any nested groups) and the example.
-
-  This allows you to run a single uniquely named example, all examples with
-  similar names, all the examples in a uniquely named group, etc, etc.
-  
-  You can also use the option more than once to specify multiple example matches.
-
-  Background:
-    Given a file named "first_spec.rb" with:
-      """
-      describe "first group" do
-        it "first example in first group" do; end
-        it "second example in first group" do; end
-      end
-      """
-    And a file named "second_spec.rb" with:
-      """
-      describe "second group" do
-        it "first example in second group" do; end
-        it "second example in second group" do; end
-      end
-      """
-    And a file named "third_spec.rb" with:
-      """
-      describe "third group" do
-        it "first example in third group" do; end
-        context "nested group" do
-          it "first example in nested group" do; end
-          it "second example in nested group" do; end
-        end
-      end
-      """
-    And a file named "fourth_spec.rb" with:
-      """
-      describe Array do
-        describe "#length" do
-          it "is the number of items" do
-            Array.new([1,2,3]).length.should eq 3
-          end
-        end
-      end
-      """
-
-  Scenario: no matches
-    When I run `rspec . --example nothing_like_this`
-    Then the examples should all pass
-
-  Scenario: match on one word
-    When I run `rspec . --example example`
-    Then the examples should all pass
-
-  Scenario: one match in each context
-    When I run `rspec . --example 'first example'`
-    Then the examples should all pass
-
-  Scenario: one match in one file using just the example name
-    When I run `rspec . --example 'first example in first group'`
-    Then the examples should all pass
-
-  Scenario: one match in one file using the example name and the group name
-    When I run `rspec . --example 'first group first example in first group'`
-    Then the examples should all pass
-
-  Scenario: one match in one file using regexp
-    When I run `rspec . --example 'first .* first example'`
-    Then the examples should all pass
-
-  Scenario: all examples in one group
-    When I run `rspec . --example 'first group'`
-    Then the examples should all pass
-
-  Scenario: one match in one file with group name
-    When I run `rspec . --example 'second group first example'`
-    Then the examples should all pass
-
-  Scenario: all examples in one group including examples in nested groups
-    When I run `rspec . --example 'third group'`
-    Then the examples should all pass
-
-  Scenario: Object#method
-    When I run `rspec . --example 'Array#length'`
-    Then the examples should all pass
-    
-  Scenario: Multiple applications of example name option
-    When I run `rspec . --example 'first group' --example 'second group' --format d`
-    Then the examples should all pass
-    And the output should contain all of these:
-      |first example in first group|
-      |second example in first group|
-      |first example in second group|
-      |second example in second group|
-    And the output should not contain any of these:
-      |first example in third group|
-      |nested group first example in nested group|
-      |nested group second example in nested group|

data/features/command_line/exit_status.feature

@@ -1,83 +0,0 @@
-Feature: exit status
-
-  The rspec command exits with an exit status of 0 if all examples pass,
-  and 1 if any examples fail. The failure exit code can be overridden
-  using the --failure-exit-code option.
-
-  Scenario: exit with 0 when all examples pass
-    Given a file named "ok_spec.rb" with:
-      """
-      describe "ok" do
-        it "passes" do
-        end
-      end
-      """
-    When I run `rspec ok_spec.rb`
-    Then the exit status should be 0
-    And the examples should all pass
-
-  Scenario: exit with 1 when one example fails
-    Given a file named "ko_spec.rb" with:
-      """
-      describe "KO" do
-        it "fails" do
-          raise "KO"
-        end
-      end
-      """
-    When I run `rspec ko_spec.rb`
-    Then the exit status should be 1
-    And the output should contain "1 example, 1 failure"
-
-  Scenario: exit with 1 when a nested examples fails
-    Given a file named "nested_ko_spec.rb" with:
-      """
-      describe "KO" do
-        describe "nested" do
-          it "fails" do
-            raise "KO"
-          end
-        end
-      end
-      """
-    When I run `rspec nested_ko_spec.rb`
-    Then the exit status should be 1
-    And the output should contain "1 example, 1 failure"
-
-  Scenario: exit with 0 when no examples are run
-    Given a file named "a_no_examples_spec.rb" with:
-      """
-      """
-    When I run `rspec a_no_examples_spec.rb`
-    Then the exit status should be 0
-    And the output should contain "0 examples"
-
-  Scenario: exit with 2 when one example fails and --failure-exit-code is 2
-    Given a file named "ko_spec.rb" with:
-      """
-      describe "KO" do
-        it "fails" do
-          raise "KO"
-        end
-      end
-      """
-    When I run `rspec --failure-exit-code 2 ko_spec.rb`
-    Then the exit status should be 2
-    And the output should contain "1 example, 1 failure"
-
-  @wip
-  Scenario: exit with rspec's exit code when an at_exit hook is added upstream
-    Given a file named "exit_at_spec.rb" with:
-      """
-      require 'rspec/autorun'
-
-      describe "exit 0 at_exit" do
-        it "does not interfere with rspec's exit code" do
-          at_exit { exit 0 }
-          fail
-        end
-      end
-      """
-    When I run `rspec exit_at_spec.rb`
-    Then the exit status should be 1
-    And the output should contain "1 example, 1 failure"