-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
as_new_record not working? #22
Comments
Yes: http://github.com/rspec/rspec-rails/blob/master/lib/rspec/rails/mocks.rb#L23 Not sure why it's not working - is that really all the code you've got? |
Sorry I was a bit in a rush yesterday.
I have not much more to report. I also noticed that form_for expects #to_key to return something and mock_model does not seem to take care of that. But that's another problem. |
That's what I get for copying over the rspec-1 code without the specs! Turns out to be a bug that was recently introduced in rspec-mocks. Will be fixed before the next beta release (soon). |
OK - the as_new_record issue is fixed in rspec-mocks and will be part of the beta.6 release. I'll add a separate issue for #to_key. Separate issues should be documented in separate issues. |
Thank you very much. Sorry for the separate issue. I'll be more careful next time :) |
I appreciate it - makes it less likely for things to fall off the radar. |
Hi!
Is it implemented yet?
The text was updated successfully, but these errors were encountered: