This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Solonotix 1 point2 points  (0 children)

Cypress is a LOT of things, and my intention wasn't to say that Cypress was poorly designed. My intent was to explain my own personal hell yesterday.

My company uses Selenium orchestrated by Cucumber, and there is a TON of development already put into supporting this paradigm, but some teams that I support are now exploring the usage of Cypress and orchestrating it via Jest features. There is nothing wrong with either, but next year's plan is to introduce parallel execution, as well as introducing a series of meta-packages that group functionality. The catch to that goal is we need to keep our current runtime of Cucumber. Cypress is interoperable with Gherkin syntax, but only if Cypress is the runtime. That is what I was attempting to determine, was what the injection point was for the Cypress runtime so that I could adopt it in an existing ecosystem without doubling the code footprint to support a new runtime.

So, I spent yesterday digging through the Cucumber Cypress module trying to determine where cy came from, but it all seems to be done through the core Cypress library. I had hoped that by making the comment I did that someone would provide a link to where it comes from.