### rspec-core-2.2.0
[full changelog](http://github.com/rspec/rspec-core/compare/v2.1.0...master)
* Deprecations/changes
* --debug/-d on command line is deprecated and now has no effect
* win32console is now ignored; Windows users must use ANSICON for color
support
(Bosko Ivanisevic)
* Enhancements
* Raise exception with helpful message when rspec-1 is loaded alongside
rspec-2 (Justin Ko)
* debugger statements _just work_ as long as ruby-debug is installed
* otherwise you get warned, but not fired
* Expose example.metadata in around hooks
* Performance improvments (see
[Upgrade.markdown](https://github.com/rspec/rspec-core/blob/master/Upgrade.markdown))
* Bug fixes
* Make sure --fail-fast makes it across drb
* Pass -Ilib:spec to rcov
### rspec-mocks-2.2.0
[full changelog](http://github.com/rspec/rspec-mocks/compare/v2.1.0...v2.2.0)
* Enhancements
* Added "rspec/mocks/standalone" for exploring the rspec-mocks in
irb.
* Bug fix
* Eliminate warning on splat args without parens (Gioele Barabucci)
* Fix bug where obj.should_receive(:foo).with(stub.as_null_object) would
pass with a false positive.
### rspec-rails-2.2.0
[full changelog](http://github.com/rspec/rspec-rails/compare/v2.1.0...master)
* Enhancements
* Added stub_template in view specs
* Bug fixes
* Properly include helpers in views (Jonathan del Strother)
* Fix bug in which method missing led to a stack overflow
* Fix stack overflow in request specs with open_session
* Fix stack overflow in any spec when method_missing was invoked
* Add gem dependency on rails ~> 3.0.0 (ensures bundler won''t
install
rspec-rails-2 with rails-2 apps).
David, it''s been a while since I said Thank You, so I just want to say Thank You for everything you do for rspec. :) --linoj On Nov 28, 2010, at 5:35 PM, David Chelimsky wrote:> ### rspec-core-2.2.0 > > [full changelog](http://github.com/rspec/rspec-core/compare/v2.1.0...master) > > * Deprecations/changes > * --debug/-d on command line is deprecated and now has no effect > * win32console is now ignored; Windows users must use ANSICON for color support > (Bosko Ivanisevic) > > * Enhancements > * Raise exception with helpful message when rspec-1 is loaded alongside > rspec-2 (Justin Ko) > * debugger statements _just work_ as long as ruby-debug is installed > * otherwise you get warned, but not fired > * Expose example.metadata in around hooks > * Performance improvments (see [Upgrade.markdown](https://github.com/rspec/rspec-core/blob/master/Upgrade.markdown)) > > * Bug fixes > * Make sure --fail-fast makes it across drb > * Pass -Ilib:spec to rcov > > ### rspec-mocks-2.2.0 > > [full changelog](http://github.com/rspec/rspec-mocks/compare/v2.1.0...v2.2.0) > > * Enhancements > * Added "rspec/mocks/standalone" for exploring the rspec-mocks in irb. > > * Bug fix > * Eliminate warning on splat args without parens (Gioele Barabucci) > * Fix bug where obj.should_receive(:foo).with(stub.as_null_object) would > pass with a false positive. > > ### rspec-rails-2.2.0 > > [full changelog](http://github.com/rspec/rspec-rails/compare/v2.1.0...master) > > * Enhancements > * Added stub_template in view specs > > * Bug fixes > * Properly include helpers in views (Jonathan del Strother) > * Fix bug in which method missing led to a stack overflow > * Fix stack overflow in request specs with open_session > * Fix stack overflow in any spec when method_missing was invoked > * Add gem dependency on rails ~> 3.0.0 (ensures bundler won''t install > rspec-rails-2 with rails-2 apps). > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users-- jonathan linowes parkerhill technology group llc jonathan at parkerhill.com office: 603-838-2884 tech blog: http://vaporbase.com personal tumblog: http://jon.linow.es facebook: http://facebook.com/jon.linowes twitter: @linojon
On Nov 28, 2010, at 4:35 PM, David Chelimsky wrote:> ### rspec-core-2.2.0 > > > * Performance improvments (see [Upgrade.markdown](https://github.com/rspec/rspec-core/blob/master/Upgrade.markdown))Wow, the perf improvements are *much* appreciated! My test suite (MRI 1.9.2p0) with 3300 examples went from 7.4s under 2.1.0 to 3.2s with 2.2.1. Most excellent! cr
On Nov 29, 2010, at 8:04 AM, Chuck Remes wrote:> > On Nov 28, 2010, at 4:35 PM, David Chelimsky wrote: > >> ### rspec-core-2.2.0 >> >> >> * Performance improvments (see [Upgrade.markdown](https://github.com/rspec/rspec-core/blob/master/Upgrade.markdown)) > > Wow, the perf improvements are *much* appreciated! > > My test suite (MRI 1.9.2p0) with 3300 examples went from 7.4s under 2.1.0 to 3.2s with 2.2.1. Most excellent!Glad to hear it. My benchmarks were based on an essentially empty spec suite (so no overhead from the implementation code). Hearing that with a real app we''re still getting 1k examples per second makes me very happy :) I''m assuming, however, this is not a Rails app, correct?
On Nov 29, 2010, at 9:27 AM, David Chelimsky wrote:> On Nov 29, 2010, at 8:04 AM, Chuck Remes wrote: > >> >> On Nov 28, 2010, at 4:35 PM, David Chelimsky wrote: >> >>> ### rspec-core-2.2.0 >>> >>> >>> * Performance improvments (see [Upgrade.markdown](https://github.com/rspec/rspec-core/blob/master/Upgrade.markdown)) >> >> Wow, the perf improvements are *much* appreciated! >> >> My test suite (MRI 1.9.2p0) with 3300 examples went from 7.4s under 2.1.0 to 3.2s with 2.2.1. Most excellent! > > Glad to hear it. My benchmarks were based on an essentially empty spec suite (so no overhead from the implementation code). Hearing that with a real app we''re still getting 1k examples per second makes me very happy :) I''m assuming, however, this is not a Rails app, correct?Correct, this is not a rails app. I write straight-up ruby code. :) cr