forked from Klaveness-Digital/cypress-cucumber-preprocessor
-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Using ES6 Template Literal Syntax in DocStrings causes critical error #415
Labels
Comments
ralphsaunders
referenced
this issue
in ralphsaunders/cypress-cucumber-preprocessor
Jul 18, 2020
Suggested fix. Unfortunately test case still fails. re #415
ralphsaunders
referenced
this issue
in ralphsaunders/cypress-cucumber-preprocessor
Jul 18, 2020
All test cases now passing fix #415
lgandecki
pushed a commit
that referenced
this issue
Jul 19, 2020
Suggested fix. Unfortunately test case still fails. re #415
🎉 This issue has been resolved in version 2.5.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behaviour
Crafting a DocString containing ES6 template literal syntax will cause an error in Cypress and block all tests from running.
Desired behaviour
Desired behaviour is that strings containing ES6 template literals are just strings and can be handled as strings in step implementations.
Test code to reproduce
Any .feature definitions with the following DocString will throw an error as Cypress attempts to parse the template literal.
Versions
The text was updated successfully, but these errors were encountered: