Gherkin
Gherkin copied to clipboard
Behat
Gherkin parser, written in PHP for Behat project
Our lexer bails out when a non-UTF-8 encoding is encountered. Cucumber supports a header similar to the language one, that causes the file to be converted (outside of the parser)...
When we have a background description, it's captured as part of the background's title Removing this line produces a failing test https://github.com/Behat/Gherkin/blob/38b23b36b563c1967aeaa3ab622aa6b700bae4e7/tests/Cucumber/CompatibilityTest.php#L44
We error out if there's no feature in a file, whereas cucumber silently returns null Not sure the impact this has or whether it's worth fixing Removing this line will...
Hi! I just noticed that the filters (`Behat\Gherkin\Filter\RoleFilter` for example) has the `as an` string hardcoded. This makes it imposible to use some role-based features in other languages. Update: It...
Cucumber repo has an example with an unknown language, which should cause a parse error. We default back to `en` I believe
It looks like it uses a syntax from an older version of cucumber.
We do things slightly differently to cucumber, removing this line will cause a failing test https://github.com/Behat/Gherkin/blob/master/tests/Behat/Gherkin/Cucumber/CompatibilityTest.php#L36
I have Behat test cases written like so: Feature: Checkout In order to buy products As a customer I need to be able to checkout items in the cart Background:...
Checking the parsing examples from Gherkin, the following fail due to issues with scenario outlines: * ~[descriptions.feature](https://github.com/cucumber/cucumber/blob/master/gherkin/testdata/good/descriptions.feature) - the description on the final Example causes a parse error~ [moved to...