Allow upcoming rspec-expectations 4.x to be used #789
Conversation
This file contains 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
|
Current plans for RSpec are to keep the current cucumber + aruba dependencies and only upgrade after the 4.0 release. This means this PR can be on hold until then. |
|
When RSpec 4 is released, Aruba should be tested with both 3 and 4. |
olleolleolle
approved these changes
Apr 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Loosen dependency on rspec-expections to allow version 4.x
Motivation and Context
This prepares Aruba for the upcoming RSpec 4.0, and will allow Aruba 1.x to be
used to test that release.
How Has This Been Tested?
This was split off from #787 so has been tested in CI already.
Types of changes