-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
And step not being recognised as a step in feature file #88
Comments
me too , I even tried given the concrete path to test if my expression was problematic -- but same results π’ |
The Gherkin language has the step keywords I didn't know Cypress exposes You should be able to rename your We could of course add support for recognising I'd rather add a note in the docs that Cypress users should avoid using these keywords. Would that work for you? |
Thanks for the response and explanation. I had a look at the Cucumber documentation and it seems that Cucumber does recognise It seems that there could be value in adding support for |
The /cc @badeball |
I'm closing this as I am convinced the fix should be in |
π What did you see?
And step not being recognised as a step in feature file.
β What did you expect to see?
And steps found in TypeScript file and no warning messages.
π¦ Which tool/library version are you using?
Cucumber VS Code extension -
v1.2.11
VS Code -
v1.70.2
macOS Monterey -
v12.5.1 (21G83)
π¬ How could we reproduce it?
testing/e2e/cypress/integration/change-password.feature
testing/e2e/cypress/integration/change-password/change-password.ts
π Any additional context?
settings.json:
This text was originally generated from a template, then edited by hand. You can modify the template here.
The text was updated successfully, but these errors were encountered: