Upgrade to RSpec 2.x has been more painful than i expected. A lot more
painful.
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
end
def ok?
true
end
end
It is passing in RSpec 1.3. See the original discussion of that
feature that i myself suggested/needed
http://groups.google.com/group/rspec/browse_thread/thread/89d6dd78b8f76df7/21109b78fc61a0e6
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
https://github.com/dchelimsky/rspec/blob/master/spec/spec/example/example_methods_spec.rb
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
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
