You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
acceptance: .built $(TOKENS)$(ASTS)$(PICKLES)$(ERRORS)$(SOURCES)## Build acceptance test dir and compare results with reference
This is a problem because:
As of May 2016 Gherkin is implemented in 8 languages. This number is likely to increase to a dozen within a year or two. Very few programmers are intimate with all those languages. Therefore, in order to make it as easy as possible to refactor, fix bugs, add features and release packages it is essential that all implementations have a similar structure.
🤔 What's the problem you've observed?
The acceptance tests for Javascript currently do verify if the parser produces the right tokens:
gherkin/javascript/Makefile
Lines 13 to 16 in 1cc2ef0
gherkin/java/Makefile
Line 42 in 1cc2ef0
Compare with:
gherkin/java/Makefile
Lines 13 to 17 in 1cc2ef0
gherkin/java/Makefile
Line 42 in 1cc2ef0
This is a problem because:
CONTRIBUTING.md - consistency between implementations
✨ Do you have a proposal for making it better?
Include the tokens in the acceptance tests again.
📚 Any additional context?
The tokens were removed with cucumber/common#448 and never put back once reverted.
The text was updated successfully, but these errors were encountered: