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
{{ message }}
This repository has been archived by the owner on Apr 6, 2020. It is now read-only.
I believe that this tool adds an unnecessary and problematic level of abstraction on top of Cypress' already great API.
Using a templated set of scenario steps rarely covers 100% of use cases, so there would always be a mix of Gherkin and Cypress code for most test suites. Having to maintain and support 2 different styles of test writing seems less ideal than writing all tests in Cypress. Writing all tests in Cypress is relatively simple—even compared to Gherkin—but offers much more flexibility.
Finally, you can continue to write tests as Gherkin scenarios by using other tools like cypress-cucumber-preprocessor—which cypress-scenario-runner uses under the hood, in fact. That could give you the best of both worlds: flexibility in test writing with the readability of Gherkin.
The text was updated successfully, but these errors were encountered:
I believe that this tool adds an unnecessary and problematic level of abstraction on top of Cypress' already great API.
Using a templated set of scenario steps rarely covers 100% of use cases, so there would always be a mix of Gherkin and Cypress code for most test suites. Having to maintain and support 2 different styles of test writing seems less ideal than writing all tests in Cypress. Writing all tests in Cypress is relatively simple—even compared to Gherkin—but offers much more flexibility.
Finally, you can continue to write tests as Gherkin scenarios by using other tools like
cypress-cucumber-preprocessor
—whichcypress-scenario-runner
uses under the hood, in fact. That could give you the best of both worlds: flexibility in test writing with the readability of Gherkin.The text was updated successfully, but these errors were encountered: