6 ms·
I used to have troubles with UI tests too, but then I discovered Cypress (https://www.cypress.io/ https://www.cypress.io/). You can still run into an issue once
by GvS 7y ago
I used to have troubles with UI tests too, but then I discovered Cypress (https://www.cypress.io/ https://www.cypress.io/). You can still run into an issue once in a while, but it's way better than anything else and it's getting even better with each release.
- mavelikara 7y agoAfter reading through the website and watching their video, I still don't understand how it works out what it's value proposition is. Is there some demo where I can see and understand how Cypress provides value over the state of the art?
- Macha 7y agoIt solves the same problem as Selenium without actually being Selenium. The one time Selenium was reliable in my company was when our team had a dedicated, massively overprovisioned grid. The biggest pro is it just has less random "Oh, guess that timed out?" issues than when we used Selenium. The biggest negative is it's chrome only.
- karldcampbell 7y agoHave you looked into TestCafe[1]? I've only used it for a PoC, but it has better browser support than Cypress. [1]https://devexpress.github.io/testcafe/ https://devexpress.github.io/testcafe/
- mping 7y agoCypress aims to be as deterministic as possible. You can write tests that wait for a specific xhr request or even mock them. The combination of that and the promise based API makes it much more reliable than selenium. In practice, I have had much less flakiness in my Cypress tests than with selenium or other webdriver API.