[rspec-users] Upgrade problems/questions regarding RSpec 1.3.0 to 2.0.1

Jarmo Pertman jarmo.p at gmail.com
Thu Nov 4 20:18:15 EDT 2010

Upgrade to RSpec 2.x has been more painful than i expected. A lot more

Subject#subject behavior with "self" is also broken!

This fails in RSpec 2 with stack overflow:
describe "something" do
  subject { self }

  it "is ok?" do
    should be_ok

  def ok?

It is passing in RSpec 1.3. See the original discussion of that
feature that i myself suggested/needed

It also seems to me that the #subject specs provided with the patch
for 1.x have been deleted also during some refactoring or something.
At least i couldn't find the specs testing that explicit functionality
from rspec-core. They still exist at 1.x repo though

I'm really sorry if some of the problems in this thread are already
fixed in master, but i couldn't see any open bugs relating to any of
the problems described here.

Waiting for some solutions-explanations how to solve most of the
problems hopefully.

Jarmo Pertman
IT does really matter - http://www.itreallymatters.net

More information about the rspec-users mailing list