rspec-core-2.6.3 is released!
May 24th, 2011
This is a bug fix release that should install correctly regardless of which version of rubygems you are running.
rspec-core-2.6.3 / 2011-05-24
- Bug fixes
- Explicitly convert exit code to integer, avoiding TypeError when return
value of run is IO object proxied by
DRb::DRbObject(Julian Scheid) - Clarify behavior of
--examplecommand line option - Build using a rubygems-1.6.2 to avoid downstream yaml parsing error
- Explicitly convert exit code to integer, avoiding TypeError when return
value of run is IO object proxied by
rspec-rails-2.6.1.beta1 is released!
May 22nd, 2011
This is a beta release intended to provide something that works with
rails-3.1.0.rc1. It is not compatible with rails-3.1.0.beta1 or
rake-0.9.0 (make sure you specify rake-0.8.7 in your Gemfile), but it is
compatible with every other release of rails from 3.0.0 through
3.1.0.rc1.
rspec-rails-2.6.1.beta1 / 2011-05-22
This release is compatible with rails-3.1.0.rc1, but not rails-3.1.0.beta1
- Bug fixes
- fix controller specs with anonymous controllers with around filters
- exclude spec directory from rcov metrics
- guard against calling prerequisites on nil default rake task (Jack Dempsey)
rspec-core-2.6.1 is released!
May 19th, 2011
This is a bug fix release, restoring integration with with rcov.
- Bug fixes
- Don’t extend nil when filters are nil
require 'rspec/autorun'when running rcov.
rspec-2.6.0 is released
May 12th, 2011
rspec-core-2.6.0
Enhancements
shared_context(Damian Nurzynski)- extend groups matching specific metadata with:
- method definitions
- subject declarations
- let/let! declarations
- etc (anything you can do in a group)
- extend groups matching specific metadata with:
its([:key])works for any subject with #[]. (Peter Jaros)treat_symbols_as_metadata_keys_with_true_values(Myron Marston)- Print a deprecation warning when you configure RSpec after defining an example. All configuration should happen before any examples are defined. (Myron Marston)
- Pass the exit status of a DRb run to the invoking process. This causes specs run via DRb to not just return true or false. (Ilkka Laukkanen)
- Refactoring of
ConfigurationOptions#parse_options(Rodrigo Rosenfeld Rosas) - Report excluded filters in runner output (tip from andyl)
- Clean up messages for filters/tags.
- Restore –pattern/-P command line option from rspec-1
- Support false as well as true in config.full_backtrace= (Andreas Tolf Tolfsen)
Bug fixes
- Don’t stumble over an exception without a message (Hans Hasselberg)
- Remove non-ascii characters from comments that were choking rcov (Geoffrey Byers)
- Fixed backtrace so it doesn’t include lines from before the autorun at_exit hook (Myron Marston)
- Include RSpec::Matchers when first example group is defined, rather than just before running the examples. This works around an obscure bug in ruby 1.9 that can cause infinite recursion. (Myron Marston)
- Don’t send
example_group_[started|finished]to formatters for empty groups. - Get specs passing on jruby (Sidu Ponnappa)
- Fix bug where mixing nested groups and outer-level examples gave unpredictable :line_number behavior (Artur Małecki)
- Regexp.escape the argument to –example (tip from Elliot Winkler)
- Correctly pass/fail pending block with message expectations
- CommandLine returns exit status (0/1) instead of true/false
- Create path to formatter output file if it doesn’t exist (marekj).
rspec-expectations-2.6.0
Enhancments
changematcher accepts Regexps (Robert Davis)- better descriptions for have_xxx matchers (Magnus Bergmark)
- range.should cover(*values) (Anders Furseth)
Bug fixes
- Removed non-ascii characters that were choking rcov (Geoffrey Byers)
- change matcher dups arrays and hashes so their before/after states can be compared correctly.
- Fix the order of inclusion of RSpec::Matchers in Test::Unit::TestCase and MiniTest::Unit::TestCase to prevent a SystemStackError (Myron Marston)
rspec-mocks-2.6.0
Enhancements
- Add support for
any_instance.stubandany_instance.should_receive(Sidu Ponnappa and Andy Lindeman)
- Add support for
Bug fixes
- fix bug in which multiple chains with shared messages ending in hashes failed to return the correct value
rspec-rails-2.6.0
Enhancements
- rails 3 shortcuts for routing specs (Joe Fiorini)
- support nested resources in generators (Tim McEwan)
- require ‘rspec/rails/mocks’ to use
mock_modelwithout requiring the whole rails framework - Update the controller spec generated by the rails scaffold generator:
- Add documentation to the generated spec
- Use
any_instanceto avoid stubbing finders - Use real objects instead of
mock_model - Update capybara integration to work with capy 0.4 and 1.0.0.beta
- Decorate paths passed to
[append|prepend]_view_pathswith empty templates unless rendering views. (Mark Turner)
Bug fixes
- fix typo in “rake spec:statsetup” (Curtis Schofield)
- expose named routes in anonymous controller specs (Andy Lindeman)
- error when generating namespaced scaffold resources (Andy Lindeman)
- Fix load order issue w/ Capybara (oleg dashevskii)
- Fix monkey patches that broke due to internal changes in rails-3.1.0.beta1
rspec-2.6.0.rc6 is released!
May 6th, 2011
We’re doing one more release candidate to update rspec-rails to work with rails-3.1.0.beta1. This will hopefully be the last release candidate, with a final release coming in just a few days.
rspec-rails-2.6.0.rc6
- Bug fixes
- Fix load order issue w/ Capybara (oleg dashevskii)
- Relax the dependencies on rails gems to >= 3.0 (Joel Moss)
- Fix monkey patches that broke due to internal changes in rails-3.1.0.beta1
rspec-core-2.6.0.rc6
- Enhancements
- Restore –pattern/-P command line option from rspec-1
- Support false as well as true in config.full_backtrace= (Andreas Tolf Tolfsen)
rspec-2.6.0.rc4 is released!
May 1st, 2011
This release addresses issues that were raised in the rspec-core-2.6.0.rc2 release.
NOTE: this was originally released as rc3, but there was a problem related to rubygems that made it uninstallable.
rspec-core-2.6.0.rc4
Enhancements
- Clean up messages for filters/tags.
rspec-mocks-2.6.0.rc4
Bug fixes
- Support multiple calls to any_instance in the same example (Sidu Ponnappa)
rspec-rails-2.6.0.rc4
Enhancements
- Update the controller spec generated by the rails scaffold generator:
- Add documentation to the generated spec
- Use
any_instanceto avoid stubbing finders - Use real objects instead of
mock_model
- Update capybara integration to work with capy 0.4 and 1.0.0.beta
- Decorate paths passed to
[append|prepend]_view_pathswith empty templates unless rendering views. (Mark Turner)
rspec-2.6.0.rc3 is released!
April 30th, 2011
UPDATE: there was a problem related to rubygems that made this release uninstallable, so it’s been yanked and rc4 has been released.
This release addresses issues that were raised in the rspec-core-2.6.0.rc2 release.
rspec-core-2.6.0.rc3
Enhancements
- Clean up messages for filters/tags.
rspec-mocks-2.6.0.rc3
Bug fixes
- Support multiple calls to any_instance in the same example (Sidu Ponnappa)
rspec-rails-2.6.0.rc3
Enhancements
- Update the controller spec generated by the rails scaffold generator:
- Add documentation to the generated spec
- Use
any_instanceto avoid stubbing finders - Use real objects instead of
mock_model
- Update capybara integration to work with capy 0.4 and 1.0.0.beta
- Decorate paths passed to
[append|prepend]_view_pathswith empty templates unless rendering views. (Mark Turner)
rspec-2.6.0.rc2 is released!
April 18th, 2011
We’re releasing rspec-2.6.0.rc2 as a release candidate as there are some internal changes that we’d like to see put through their paces before doing a final release. Note that the changes I speak of are internal. There are no new deprecations in this release, nor any backward-incompatible changes.
There are, however, some new features that we’re really excited about. Please do check it out and please do report any issues to the appropriate github issue tracker:
rspec-core-2.6.0.rc2
Enhancements
shared_context(Damian Nurzynski)- extend groups matching specific metadata with:
- method definitions
- subject declarations
- let/let! declarations
- etc (anything you can do in a group)
- extend groups matching specific metadata with:
its([:key])works for any subject with #[]. (Peter Jaros)treat_symbols_as_metadata_keys_with_true_values(Myron Marston)- Print a deprecation warning when you configure RSpec after defining an example. All configuration should happen before any examples are defined. (Myron Marston)
- Pass the exit status of a DRb run to the invoking process. This causes specs run via DRb to not just return true or false. (Ilkka Laukkanen)
- Refactoring of ConfigurationOptions#parse_options (Rodrigo Rosenfeld Rosas)
- Report excluded filters in runner output (tip from andyl)
Bug fixes
- Don’t stumble over an exception without a message (Hans Hasselberg)
- Remove non-ascii characters from comments that were choking rcov (Geoffrey Byers)
- Fixed backtrace so it doesn’t include lines from before the autorun at_exit hook (Myron Marston)
- Include RSpec::Matchers when first example group is defined, rather than just before running the examples. This works around an obscure bug in ruby 1.9 that can cause infinite recursion. (Myron Marston)
- Don’t send example_group_[started|finished] to formatters for empty groups.
- Get specs passing on jruby (Sidu Ponnappa)
- Fix bug where mixing nested groups and outer-level examples gave unpredictable :line_number behavior (Artur Małecki)
- Regexp.escape the argument to –example (tip from Elliot Winkler)
- Correctly pass/fail pending block with message expectations
rspec-expectations-2.6.0.rc2
Enhancments
changematcher accepts Regexps (Robert Davis)- better descriptions for have_xxx matchers (Magnus Bergmark)
Bug fixes
- Removed non-ascii characters that were choking rcov (Geoffrey Byers)
- change matcher dups arrays and hashes so their before/after states can be compared correctly.
- Fix the order of inclusion of RSpec::Matchers in Test::Unit::TestCase and MiniTest::Unit::TestCase to prevent a SystemStackError (Myron Marston)
rspec-mocks-2.6.0.rc2
Enhancements
- Add support for any_instance.stub and any_instance.should_receive (Sidu Ponnappa and Andy Lindeman)
Bug fixes
- fix bug in which multiple chains with shared messages ending in hashes failed to return the correct value
rspec-rails-2.6.0.rc2
Enhancments
- rails 3 shortcuts for routing specs (Joe Fiorini)
- support nested resources in generators (Tim McEwan)
- require ‘rspec/rails/mocks’ to use
mock_modelwithout requiring the whole rails framework
Bug fixes
- fix typo in “rake spec:statsetup” (Curtis Schofield)
- expose named routes in anonymous controller specs (Andy Lindeman)
- error when generating namespaced scaffold resources (Andy Lindeman)
rspec-1.3.2 and rspec-rails-1.3.4 are released!
April 11th, 2011
rspec-1.3.2 and rspec-rails-1.3.4 have been released!
This is primarily a bug-fix release of the rspec-1.x series, and is recommended for all users who have not yet upgraded to rspec-2.
rspec-rails-1.3 users will need to upgrade to rspec-rails-1.3.4, which depends on rspec ~> 1.3.2 (meaning 1.3.2 and up, but not 2.0).
rspec 1.3.2
Enhancements
- Raise a meaningful error when an argument-scoped stub is called with the wrong args (Alexey)
- Dev: ignore .rbc files (Myron Marston)
Bug fixes
- Fix regression in which an expectation should return the value from a previously defined stub of the same method (Tom Stuart)
- Support heckling class methods (Dan Kubb)
- Only try to pass messages to the superclass if the superclass responds to the method (Andrew Selder)
rspec-rails-1.3.4 is released!
rspec-rails 1.3.4
- No new code
- Depends on rspec ~> 1.3.2
- rspec-rails 1.3.3 depended on rspec-1.3.1 explicitly, so this release allows you to upgrade to rspec-1.3.2 with rspec-rails.
rspec-core-2.5.1 is released!
February 6th, 2011
rspec-core-2.5.1
This release breaks compatibility with rspec/autotest/bundler integration, but does so in order to greatly simplify it.
With the release of rspec-core-2.5.1, if you want the generated autotest command to include bundle exec, require Autotest’s bundler plugin in a .autotest file in the project’s root directory or in your home directory:
require "autotest/bundler"
Now you can just type ‘autotest’ on the commmand line and it will work as you expect.
If you don’t want ‘bundle exec’, there is nothing you have to do.

