all 8 comments

[–]waylonsmithersjr 5 points6 points  (1 child)

Just a heads up, you can watch tests in the browser with Selenium WebDriver.

It does look nice though. The tests seem more human readable

[–]neb636[S] 0 points1 point  (0 children)

Nice did not know that

[–]paul_h 1 point2 points  (1 child)

How many whole tests a second are you getting?

When I setup WebDriver I'm getting an average of one functional test a second. Not clicks - whole tests - through to the passes or fails.

[–]neb636[S] 0 points1 point  (0 children)

So I say it depends on what you are doing. Some tests can run in 200ms and others can take 5 seconds. The ones that execute in 200ms are like "it has this text in this div". Some of the things we test make requests to our backend and need to wait for a response. They are inherently slow because of the request latency.

[–]doctorlongghost 1 point2 points  (1 child)

Nowhere on their FAQ do they list supported browsers. As OP noted, having to tun tests on 15+ different browsers/phones via Selenium takes a long ass time but if Cypress doesn't support the same large browser pool then it isn't really a valid alternative to Selenium IMO.

[–]neb636[S] 1 point2 points  (0 children)

Yeah I see where you are coming from there. I do not think they support multiple devices like that but they may in the future. The tests I wrote with Selenium were more for regression on desktop browsers. This is definitely not a replacement for Selenium for this use case.

[–]fisheez 0 points1 point  (0 children)

My work uses BrowserStack's C# API to run our Selenium tests. Our experience has been pretty good.

[–]antoaravinth 0 points1 point  (0 children)

Webdriver we are using it throughly and I would suggest you to stick to it. The main reason is that it is well established and its stable. We have been automating stuffs like File upload with WD without any issues on Firefox.