Cypress Is Dead

Somebody: A) hasn't read the code.

B) Has no idea how much things like Cucumber and BDD/DSL'd test freworks are actually ignored by business users

C) Has unrealistic expectations about the attention to detail paid to maintaining DSL bound code by non-developers.

D) hasn't figured out the cy.intercept calls

E) Hasn't looked at Selenium and WebDriver's code either

Now, if you really want to talk Cypress warts:

Many FE devs, and most backend devs faced with a Cypress test have no idea what async programming is, and how it is drastically different from the synchronous model they are used to. There is also the oddness around the fact that Cypress is essentially a wrapper around Mocha.

They didn't structure their repo ideally, and any documentation mapping execution flow is absent. I know, because I'm one of the ones stubborn enough to stake it out.

The decision to deliver it as an Electron app certainly doesn't help things, and their debug howtos are pretty useless on my opinion without the extra context and understanding about how nodejs debugging actually works.

I also find that their offensive architecture attempt around their Dashboard offering for parallelism is an affront to the testing community. Also, their move toward GraphQL integration is strictly a bad move and enough to nudge me away.

However, despite that, it is an absolutely acceptable piece pf kit. My gripe is more with developers who expect to never have to read how something works in order to be able to use it.

That attitude/approach has never worked with anything I've used, and is unlikely to start working now.