-
-
Notifications
You must be signed in to change notification settings - Fork 9
Background may need clarification #103
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
Comments
There is a historical reason for this. When we introduced Rule, we inadvertently permitted background steps in Rules. However this was semi-contentious at the time, and not universally agreed upon by the TLC. So in essence, for now, it's a "Yes you can do it, but we don't want to recommend it". That is likely why the docs are a bit vague in this area. |
Does that mean that I think it's perfectly fine to say in a reference that something is possible but not recommended—but it must be crystal clear at all costs. In other words, that paragraph could look like this?
|
I've moved this over to website for discussion. But I think it's something we never got a consensus on. If you want to submit a PR i'll gladly review it |
I agree we should document what it does clearly even if we don't like it much. +1 to a PR, the language in your last comment seemed good. I'd also spell out that the background steps from the feature and rule would be concatenated, just to avoid any doubt. |
To clarify as well @bgusach the answer is (a). Both feature and background can have them. If just 1, use the 1, if both, use feature (background), first followed by rule (background), second |
👓 What did you see?
According to the docs:
https://cucumber.io/docs/gherkin/reference/#background
It's not clear to me whether:
a) Both feature and rule can have a background
b) Either feature or rule can have a background, but not both.
I think it's (a), but that sentence needs clarification.
✅ What did you expect to see?
Maybe something like this?
The text was updated successfully, but these errors were encountered: