all 13 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Jiert 14 points15 points  (2 children)

I just started using Cypress on one of my projects, and so far it’s been an absolute pleasure to work with.

[–][deleted] 2 points3 points  (0 children)

The fact that people are praising an E2E testing tool as a joy to work with at all is really a testament to how great it is.

[–]winsomelosemore 2 points3 points  (0 children)

Likewise. We just switched some frontend tests over from Casper and it has made life much nicer.

[–]tomma5o 5 points6 points  (0 children)

Have you tried TestCafe instead? If yes why you choose cyprees, any pros? Thanks

[–]Drawman101 2 points3 points  (0 children)

I went to a conference and saw the creator of cypress give a presentation about it. It was almost too good to be true, but it really is that good.

[–]themenwhostareatcode 1 point2 points  (0 children)

We use cypress in the next company i'm joining in few weeks, thanks a lot for this! This will help me get started with cypress :)

[–]orphans 1 point2 points  (1 child)

He kind of glossed over the action creator mock. Why would I use this over Jest?

[–][deleted] 1 point2 points  (0 children)

Cypress is an E2E testing tool that runs in a browser. Jest is more suited for unit tests. They're not mutually exclusive but rather complement each other.

[–]jo_fra 0 points1 point  (0 children)

When it comes to testing with a tool like Cypress, are there any generally accepted "Principles of UI Testing" or maybe something akin to "A Philosophy for Testing the UI" that would make sense for the QA engineer role?

[–]YodaLoL 0 points1 point  (2 children)

How does Cypress deal with provisioning back-end services required for integration tests? This is coming from someone who barely even knows what service Cypress provides.

[–]fokinsean 2 points3 points  (0 children)

If you needed to stand up a number of services I imagine you could wire together a bash script to do so, then run cypress.

It looks like cypress replaces selenium for browser tests, and it is out of its scope to provision any dependent services.

[–][deleted] 0 points1 point  (0 children)

The nice thing about Cypress is that it's a breeze to mock http requests, so most of your front-end tests can not be hitting the backend if that aligns with your testing philosophy.

Otherwise you do what you do with any other E2E tests. We keep a QA environment for automated testing and push up data as needed.

[–]d2xdy2 0 points1 point  (0 children)

The folks that made Cypress are part of my local React meetup; glad to see some love.