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.

Sign up for GitHub

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

Jump to bottom

Missing feature keyword should not error #208

Open

ciaranmcnulty opened this issue Feb 4, 2021 · 0 comments

Labels

cucumber-parity

Contributor

ciaranmcnulty commented Feb 4, 2021 •

edited

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 add a failing test
https://github.com/Behat/Gherkin/blob/master/tests/Behat/Gherkin/Cucumber/CompatibilityTest.php#L37

ciaranmcnulty added the cucumber-parity label

ciaranmcnulty changed the title ~~Missing feature keyword should not create feature~~ Missing feature keyword should not error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment