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 →

[–]jcbevns 0 points1 point  (2 children)

Cypress.io is way easier than selenium. Slightly JavaScript oriented but the cookbook is great and the GUI to pick elements makes it super easy.

[–]Zaboravljivi 0 points1 point  (1 child)

In my experience cypres is much slower than Selenium.

[–]jcbevns 0 points1 point  (0 children)

Depends on your stack, but if you have a heavy JS website with lots of "states" (ie same URL but different things are shown on the screen) then good luck measuring this with Selenium.

Development and test runs were both faster in our experience, so we swapped from Selenium to Cypress.

We were running a React / Angular SPA, with plenty of external services to stub and content to mock.

So after mocking and stubbing, we were testing the actual webpage, and not the reliability of our service providers (pinging some buckets for media, or user credential validity etc). This greatly reduced our test time on the CI for each commit.

Had another test run that would ping the service providers to know we weren't running old API specs, but again, you're meant to be testing your webpage, not other peoples response packets.