Skip to content
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

Gherkin update #59

Merged
merged 6 commits into from
Nov 7, 2017
Merged

Gherkin update #59

merged 6 commits into from
Nov 7, 2017

Conversation

mlvandijk
Copy link
Member

Merge feature-introduction into gherkin-reference
Update links
Merge info from cucumber/common#68 into introduction

allow concise description of examples to illustrate business rules in most real-world
domains.
domains. It is structured enough for a tool like Cucumber to process.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about

Gherkin is designed to be easy for people to read and write, yet structured enough to
to allow for automated processing and concise description of business rules.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much better, thanks!


Cucumber does not care about the name or the description. Their purpose is simply to provide a place for you to document important aspects of the Feature, such as a brief explanation and a list of business rules (general acceptance criteria).
Cucumber does not care about the name or the description.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Slightly wary of "does not care" here. Can we reword?

Also remove "simply" ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to: "The name and the description have no special meaning to Cucumber." (and removed "simply").
Let me know if anyone has a better idea

@plaindocs
Copy link
Contributor

Otherwise looks great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants