Convert specs to RSpec 3 syntax with Transpec #619
Merged
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.
Converted suite to RSpec 3 syntax with Transpec.
Additionally, I updated a test from endpoint_spec.rb on Line 108. Test checks whether response cookies are set. Appropriate test would be to check for nil rather than using a match keyword. Previous versions of RSpec would allow checking against nil using the
=~
syntax. RSpec 3 does not allow nil to be checked with thematch
matcher. The test was updated to reflect this change.Test Before Change:
Test After Change:
This conversion is done by Transpec 1.10.4 with the following command:
transpec
from: obj.should
to: expect(obj).to
from: == expected
to: eq(expected)
from: obj.stub(:message)
to: allow(obj).to receive(:message)
from: obj.should_receive(:message)
to: expect(obj).to receive(:message)
from: obj.should_not
to: expect(obj).not_to
from: =~ /pattern/
to: match(/pattern/)
from: lambda { }.should
to: expect { }.to
from: lambda { }.should_not
to: expect { }.not_to
from: > expected
to: be > expected
from: obj.should_not_receive(:message)
to: expect(obj).not_to receive(:message)
from: >= expected
to: be >= expected