Update RSpec expectations syntax using Transpec #35
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
August 13, 2014 16:37
"DEPRECATION: mock is deprecated. Use double instead."
This conversion is done by Transpec 2.2.0 with the following command:
transpec
* 157 conversions
from: obj.should
to: expect(obj).to
* 129 conversions
from: == expected
to: eq(expected)
* 68 conversions
from: obj.should_receive(:message)
to: expect(obj).to receive(:message)
* 49 conversions
from: obj.stub(:message)
to: allow(obj).to receive(:message)
* 12 conversions
from: proc { }.should
to: expect { }.to
* 3 conversions
from: obj.should_not_receive(:message)
to: expect(obj).not_to receive(:message)
* 2 conversions
from: obj.should_not
to: expect(obj).not_to
See also: https://github.com/yujinakayama/transpec#supported-conversions
Author
|
🙋 These changes branch off #34. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
💁 The API for RSpec::Expectations has changed in v3.0. These changes update the existing tests to use the
:expectsyntax.