Hello all. Just a little frustration moment here and hoping someone can explain to me what is going on.
I had a passing view spec using >= rspec-rails2. Then after updating to 2.1.0-2.2.1 it always fails. Thinking I was crazy I built the example in the rspec book, and I get the same thing. Here is the full source: https://github.com/matthewcalebsmith/rspec_issue.git If I switch out the message.stub(:title => "the title") in "it 'renders a text field for the message title' do" with assign(:message, mock_model("Message",:title => "the title").as_new_record), everything passes. Why does the stub not work anymore? Using the stub gives this: 1) messages/new.html.erb renders a text field for the message title Failure/Error: form.should have_selector("input", expected following output to contain a <input type='text' name='message[title]' value='the title'/> tag: <form accept-charset="UTF-8" action="/messages" class="new_message" id="new_message" method="post"> <div style="margin:0;padding:0;display:inline"><input name="utf8" type="hidden" value="✓"></div> <input id="message_title" name="message[title]" size="30" type="text" value="Message_#<RSpec::Core::ExampleGroup::Nested_1:0x0000010312db68>"><input id="message_submit" name="commit" type="submit" value="Save"> Note the value="Message_#<RSpec::Core::ExampleGroup::Nested_1:0x0000010312db68>", which must be why the test fails. Is this an intentional change on how stub or assign works? Much thanks! Matt Smith -- matthewcalebsm...@gmail.com
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
