-
Notifications
You must be signed in to change notification settings - Fork 1
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
Rspec 3.1 compatibility #7
Comments
👍 |
transpec might be helpful for this http://yujinakayama.me/transpec/ |
Thanks for the bump, kinda slipped past me. I'll get on this soon. This functionality was supposed to be included in RSpec 3, I'm not sure how to turn it on though. You can definitely get full mocks, rspec-fire style, with the instance_double method... not sure about partial mocks. If something like this is in RSpec 3, upgrading with transpec is definitely the smoothest option. Probably just requires a find-and-replace like s/better_receive/should_receive/ first. |
Holy crap. Didn't know about transpec. That's great! |
Thanks, @nertzy ! Huge help. Never heard about transpec before, and it is amazing. I patched transpec to support converting better receive. The dynamic analysis isn't working yet, but the conversions seemed to work great. I hope to wrap it up and submit a pull request. https://github.com/toothrot/transpec/tree/better-receive-support |
Just an FYI for others, was looking into using Rspec 3 with this, but in my case using verifying doubles was enough. |
Rspec 2 uses APIs that are deprecated in Rails 4.2. This is fixed in Rspec 3.1 but better_receive is tied to 2.1
The text was updated successfully, but these errors were encountered: