Improve some cucumber scenarios #766
Merged
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
- Improve wording of feature description - Improve scenario naming - Improve example rspec use inside feature files
- Improve wording of feature description - Remove edge case scenarios
mvz
force-pushed
the
improve-some-scenarios
branch
from
c09898b to
3896672
Compare
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
Clean up some cucumber scenarios
Details
Improve scenario for Api#expand_path
Improve scenario for be_an_absolute_path matcher
Improve scenario for #absolute?
Motivation and Context
The continuing quest to make the automatic tests more streamlined and most of all .. faster!
Types of changes