4 ms·
I don't understand the difference between Selenium and Cypress. Is Cypress general control of the browser but just nicer somehow? Or is there a deeper disconnec
by mrslave 6y ago
I don't understand the difference between Selenium and Cypress. Is Cypress general control of the browser but just nicer somehow? Or is there a deeper disconnect in their designs/capabilities?
- fizzbuzzah2 6y agoor puppeteer.
- DaiPlusPlus 6y agoPuppeteer is Chromium-specific though.
- jitl 6y agoThat’s okay, Chrome is the only browser.
- Muromec 6y agoBut Playwright isn’t.
- svacko 6y agothere is already experimental Firefox support for a while in puppeteer https://github.com/puppeteer/puppeteer/#q-which-firefox-version-does-puppeteer-use https://github.com/puppeteer/puppeteer/#q-which-firefox-vers...
- mavelikara 6y agoHere is a good comparison published by one other Open Source and free tool in this space, Taiko: https://gauge.org/2019/08/21/how-taiko-compares-to-other-browser-automation-tools/ https://gauge.org/2019/08/21/how-taiko-compares-to-other-bro...
- sicromoft 6y agoHas anyone here used Taiko? The link above makes it sound pretty good.
- inglor 6y agoI go into the "in depth" bits of how each browser "clicks" in a few talks but basically: - Cypress solves a much easier problem (no multiple tabs, no native actions no hovers etc). - Cypress does everything in JavaScript and not with the debugger (like old versions of Selenium). - Cypress is bidirectional (like puppeteer/playwright or selenium bidi). - Cypress has very good dev tooling out of the box. See the article I wrote here: https://www.testim.io/blog/puppeteer-selenium-playwright-cypress-how-to-choose/ https://www.testim.io/blog/puppeteer-selenium-playwright-cyp...