-
Notifications
You must be signed in to change notification settings - Fork 8
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
Constants for feature paths #1701
Constants for feature paths #1701
Conversation
Pull reviewers statsStats of the last 30 days for popstellar:
|
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.
Maybe some naming improvement ?
# Paths to scenarios defined in simpleScenarios | ||
* def simpleScenario = 'classpath:be/features/utils/simpleScenarios.feature@name=' | ||
* def createLaoScenario = simpleScenario + 'valid_lao' | ||
* def createRollCallScenario = simpleScenario + 'valid_roll_call' |
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 find create
and valid
quite different and a bit confusing. Shouldn't the valid_roll_call
be renamed create_roll_call
to avoid this confusion ? Other proposition ?
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.
Good point, I forgot to change this.
…k-simone-feature-path-constants
[PoP - PoPCHA-Web-Client] Kudos, SonarCloud Quality Gate passed! |
[PoP - Be2-Scala] Kudos, SonarCloud Quality Gate passed! |
[PoP - Be1-Go] Kudos, SonarCloud Quality Gate passed! |
[PoP - Fe2-Android] Kudos, SonarCloud Quality Gate passed! |
[PoP - Fe1-Web] Kudos, SonarCloud Quality Gate passed! |
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.
LGTM
Paths to features and scenarios that are used across features are now defined as constants in
constants.feature
.This makes it easier to change paths in the future, as they will only have to be changed in one place. It also improves the readability of calls to
call read(...)
.