Ruby 1.9.1

rspec and rspec-rails >= 1.2.0 works with Ruby 1.9.1

    [david: rspec (master)]$ multiruby -S rake spec
    ...
    Passed: v1_8_6_114, 1.8.7-p72, 1.9.1-p0

    [david: example_rails_app (master)] $ multiruby -S rake rspec:pre_commit
    ...
    Passed: v1_8_6_114, 1.8.7-p72, 1.9.1-p0

Thanks to all who contributed to make this happen, especially Matthias Hennemeyer and Lasitha Ranatunga, who submitted patches and figured out where the problems were.

RSpec/Rails/Ruby1.9 and Test::Unit

As of this writing, rspec-rails running in ruby-1.9 requires test-unit-1.2.3. We’re looking to make this more flexible in a future release, but that’s what works now.

Sadly, due to the order in which things get loaded, it turns out to be a thus-far-unresolved-challenge to get test-unit-1.2.3 to load first if you have test-unit > 1.2.3 installed. Therefore, you will probably not have good results if you have installed:

• test-unit > 1.2.3
• minitest_tu_shim

If you are able to get it to work with either installed, please help out your brethren and submit patches to http://rspec.lighthouseapp.com.

Why does RSpec require test-unit 1.2.3 on Ruby 1.9?

It’s quite annoying to do `gem upgrade` and find that rspec has stopped working. It’s happened a few times now so I’m getting used to it, but still. Can’t RSpec use test-unit > 2.0?

Is there a lighthouse ticket for this?

@adamsalter