-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Unify feature file organization #602
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left mine as non-blocking comments as most of this seems like feng-shui.
Although the escaping seems a bit inconsistent, it might be a feature of aruba, if so ignore my comments.
Feature: Check | ||
Scenario: Check | ||
Given a file named "foo" with: | ||
\"\"\" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these escaped because were inside a """
already? I don't use aruba
really.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that is the reason. It's a little ugly 😞.
@@ -3,6 +3,63 @@ Feature: Check file content | |||
Background: | |||
Given I use a fixture named "cli-app" | |||
|
|||
Scenario: Check file contents with plain text | |||
Given a file named "features/non-existence.feature" with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this file called non-existence?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure. I copied this feature from master I think.
LGTM |
Summary
Re-organize feature files to match master
Details
Files were moved and minimal changes to their contents were done to get rid of some custom steps. Some less-useful feature files were removed.
Motivation and Context
Part of #598.
How Has This Been Tested?
N/A. Functionality should stay the same.
Types of changes