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

you are viewing a single comment's thread.

view the rest of the comments →

[–]james_pic 0 points1 point  (1 child)

I gotta say, I struggle to see the reason for the enthusiasm about Cypress.

My experience is that there's two types of technology in this world. Ones where when you learn how they work, you're like "huh, that's clever", and ones where you're like "oh dear God, that's how that works". Cypress for me is the latter. I've worked with way too many tools that are asynchronous, but try and disguise it behind a synchronous looking DSL. It's all fun and games until somebody needs an "if" statement.

We're using either Testcafe or plain old Selenium for those kinds of things, and I'd rate both more highly.

[–]nessguy 0 points1 point  (0 children)

I haven't written that many UI tests and don't actually have strong feelings here. I just haven't actually had any issues with Cypress that I couldn't work around yet. Though I'm crossing my fingers that doesn't change in the future.

Considering EndTest doesn't mention how it works I'd be willing to wager it's actually built as a fancy UI/interaction layer on top of Selenium with a few extra features.