Need advice about which tool to choose?Ask the StackShare community!

Cypress

1K
1.2K
+ 1
88
Selenium

9.8K
7.4K
+ 1
513
Add tool

Cypress vs Selenium: What are the differences?

Cypress: Better, faster, and more reliable testing for anything that runs in a browser. Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website; Selenium: Web Browser Automation. Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.

Cypress belongs to "Javascript Testing Framework" category of the tech stack, while Selenium can be primarily classified under "Browser Testing".

"Open source" is the primary reason why developers consider Cypress over the competitors, whereas "Automates browsers" was stated as the key factor in picking Selenium.

Selenium is an open source tool with 14.9K GitHub stars and 4.97K GitHub forks. Here's a link to Selenium's open source repository on GitHub.

MIT, Typeform, and Bukalapak are some of the popular companies that use Selenium, whereas Cypress is used by CircleCI, Intuit, and RELEX Solutions. Selenium has a broader approval, being mentioned in 777 company stacks & 443 developers stacks; compared to Cypress, which is listed in 60 company stacks and 45 developer stacks.

Advice on Cypress and Selenium
Yildiz Dila
testmanager/automation tester at medicalservice ยท | 5 upvotes ยท 97.7K views
Needs advice
on
Protractor
and
Cypress

In the company I will be building test automation framework and my new company develops apps mainly using AngularJS/TypeScript. I was planning to build Protractor-Jasmine framework but a friend of mine told me about Cypress and heard that its users are very satisfied with it. I am trying to understand the capabilities of Cypress and as the final goal to differentiate these two tools. Can anyone advice me on this in a nutshell pls...

See more
Replies (2)
Kevin Emery
QE Systems Engineer at Discovery, Inc. ยท | 3 upvotes ยท 22.1K views

I've used both Protractor and Cypress extensively. Cypress is the easier and more reliable tool, whereas Protractor is the more powerful tool. Your choice of tool should depend on your specific testing needs. Here are some advantages and disadvantages of each tool:

Cypress advantages:

  • Faster

  • More reliable (tends to throw fewer intermittent false failures)

  • Easier to read code (handles promises gracefully)

Cypress disadvantages:

  • Cannot switch between browser tabs

  • Cannot switch to iFrames

  • Cannot specify clicks or keypresses explicitly as if a real user was interacting

  • Cannot move the mouse to specific co-ordinates

  • Sometimes has trouble switching between different top-level domains, so not good for testing external links

  • Cypress is a newer tool with less extensive documentation and less community support

Protractor advantages:

  • More powerful because it is Selenium-based - it can switch between tabs, it can handle external links to other domains, it can handle iFrames, simulate keypresses and clicks, and move the mouse to specific co-ordinates within the browser.

  • More extensive community support and documentation

Protractor disadvantages:

  • Slower and more brittle - in general there is a higher likelihood of cryptic and/or intermittent errors which may cause your tests to fail even though there is nothing wrong with your application

  • For highly experienced automation engineers, the fundamental "brittle" nature of Selenium can be worked around - it can be reliable but only if you really know what you are doing

  • Less graceful handling of promises - relies on async/await or .then to manage the order of execution. Therefore it is a bit harder to read the code.

  • Harder to set up, and the method of setup impacts its reliability. For example, a hub/node configuration where the selenium jar is on a different physical machine than the browser under test will cause unreliability in your tests. Not everyone knows about this type of thing, so it's common to find Selenium frameworks that are set up poorly.

It's probably better to use Cypress if

  • you're at a smaller company and have a close relationship with developers who can help write hooks or stubs in their code to assist your testing

  • you don't need to do things like switch between tabs or test links to external top-level domains

It's probably better to use Protractor if

  • You might need to switch between tabs or test external links to other domains within the scope of your framework

  • You want to use a more accurate simulation of how a real user interacts with a browser (i.e. click at this location, type these keys)

  • You're at a company where you won't have any support from developers in writing hooks or stubs to make their code more testable in a less powerful framework like Cypress

See more
Jian Wang
Web Engineer at sentaca ยท | 1 upvotes ยท 50.9K views
Recommends

Please try Handow, the e2e tool basing on Puppeteer.

Gherkin syntax compatible

Chrome/Chromium orentied, driven by Puppeteer engine

Complete JavaScript programming

Create test suites rapidly without coding (or a little bit), basing on built-in steps library

Schedule test with plans and arrange stories with sequential stages

Fast running, execute story groups in parallel by multi-workers

Built-in single page report render

Cover page view, REST API and cookies test

https://github.com/newlifewj/handow

http://demo.shm.handow.org/reports

See more
Needs advice
on
WebdriverIO
Selenium
and
Jest
in

we are having one web application developed in Reacts.js. in the application, we have only 4 to 5 pages that we need to test. I am having experience in selenium with java. Please suggets which tool I should use. and why ............................ ............................ .............................

See more
Replies (1)
Prashanth Marappa
Senior Software Engineer at Mphasis ยท | 1 upvotes ยท 65K views
Recommends
Selenium

with the help of selenium we can automate react js for functional testing

See more
Decisions about Cypress and Selenium
Matt Wufsus
QA Engineer at Creditly ยท | 4 upvotes ยท 11.5K views

My company was looking for a testing tool that would integrate easily with AWS Amplify and quickly provide value. I created a POC for each tool we were exploring and showed it to the team (since we all want to contribute to the testing framework). Cypress was by far the easiest to go from nothing to running tests that were finding bugs in our web application.

The only difficulties I had with Cypress were working with iframes and the fact it does not currently handle new tabs. Cypress currently supports Chrome, Edge, Electron (headless) and has Firefox in beta so if IE is something you need to support, you might want to use another tool in conjunction or in place of Cypress.

Cypress is very well documented with a very responsive support team. Recently the Cypress team released the 'Real World App' as a showcase for implementing good tests with best practices.

See more
Shared insights
on
Jest
Cypress

As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.

See more
Kamil Kowalski
Lead Architect at Fresha ยท | 27 upvotes ยท 934.4K views

When you think about test automation, itโ€™s crucial to make it everyoneโ€™s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Cypress
Pros of Selenium
  • 22
    Open source
  • 16
    Great documentation
  • 15
    Fast
  • 14
    Simple usage
  • 9
    Cross Browser testing
  • 8
    Easy us with CI
  • 4
    Npm install cypress only
  • 167
    Automates browsers
  • 152
    Testing
  • 100
    Essential tool for running test automation
  • 24
    Record-Playback
  • 24
    Remote Control
  • 8
    Data crawling
  • 7
    Supports end to end testing
  • 6
    Functional testing
  • 6
    Easy set up
  • 3
    Easy to integrate with build tools
  • 3
    The Most flexible monitoring system
  • 3
    End to End Testing
  • 2
    Integration Tests
  • 2
    Comparing the performance selenium is faster than jasm
  • 2
    Record and playback
  • 2
    Compatible with Python
  • 2
    Easy to scale
  • 0
    Integrated into Selenium-Jupiter framework

Sign up to add or upvote prosMake informed product decisions

Cons of Cypress
Cons of Selenium
  • 15
    Cypress is weak at cross-browser testing
  • 11
    Switch tabs : Cypress can'nt support
  • 9
    No iFrame support
  • 8
    No xPath support
  • 8
    No file upload support
  • 8
    No page object support
  • 8
    No multiple domain support
  • 7
    No support for multiple tab control
  • 7
    Cypress doesn't support native app
  • 7
    Re-run failed tests retries not supported yet
  • 6
    No support for multiple browser control
  • 6
    No support for Safari
  • 4
    Adobe
  • 4
    $20/user/thread for reports
  • 4
    Not freeware
  • 3
    No 'WD wire protocol' support
  • 3
    Using a non-standard automation protocol
  • 5
    Flaky tests
  • 1
    Slow as needs to make browser (even with no gui)

Sign up to add or upvote consMake informed product decisions

What is Cypress?

Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.

What is Selenium?

Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Cypress?
What companies use Selenium?
See which teams inside your own company are using Cypress or Selenium.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Cypress?
What tools integrate with Selenium?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Cypress and Selenium?
TestCafe
It is a pure node.js end-to-end solution for testing web apps. It takes care of all the stages: starting browsers, running tests, gathering test results and generating reports.
Puppeteer
Puppeteer is a Node library which provides a high-level API to control headless Chrome over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome.
WebdriverIO
WebdriverIO lets you control a browser or a mobile application with just a few lines of code. Your test code will look simple, concise and easy to read.
Jest
Jest provides you with multiple layers on top of Jasmine.
Protractor
Protractor is an end-to-end test framework for Angular and AngularJS applications. Protractor runs tests against your application running in a real browser, interacting with it as a user would.
See all alternatives
Reviews of Cypress and Selenium
CTO at Apna Inc
Review of
Selenium

we at www.cloudqa.io use selenium hub and node architecture to execute our test cases its a very powerful tool to automate web applications.

How developers use Cypress and Selenium
Kang Hyeon Ku uses
Selenium

๊ฐ€์žฅ ๊ฐ•๋ ฅํ•œ ์›น UI / UX ํ…Œ์ŠคํŠธ ํˆด ์ด์ง€๋งŒ, ๋ฌธ์ œ๋„ ๋งŽ๋‹ค. iframe ์•ˆ์— ์žˆ๋Š” ๊ฑด ์ž˜ select ๊ฐ€ ์•ˆ๋˜๊ธฐ๋„ ํ•˜๊ณ , ํ™”๋ฉด์ด ์ž‘์•„ ์ปดํฌ๋„ŒํŠธ๊ฐ€ ํ™”๋ฉด์— ๋ณด์ด์ง€ ์•Š์œผ๋ฉด ๋˜ select ํ•  ์ˆ˜ ์—†๋‹ค. ํ•˜์ง€๋งŒ ๋ธŒ๋ผ์šฐ์ €๋ฅผ ์žˆ๋Š” ๊ทธ๋Œ€๋กœ ์ œ์–ด ํ•  ์ˆ˜ ์žˆ๋‹ค๋Š” ๊ฒŒ ๊ฐ€์žฅ ํฐ ๋งค๋ ฅ์ด๋‹ค.

ps. selenide ์™€ ๊ฐ™์ด ์“ฐ๋ฉด ์ฝ”๋“œ๊ฐ€ ๋งŽ์ด ๊ฐœ์„ ๋œ๋‹ค.

samdfonseca uses
Selenium

Maintaining and expanding automated regression tests is one of my primary responsibilities at CrowdTwist. We use Selenium to test the front-end parts of our platform.

Ralic Lo uses
Selenium

Used Selenium web-driver for automated QA testing in continuous integration and continuous deployment.

Owen Miller uses
Selenium
  • Navigating our site for tests
  • Navigating other sites that discriminate against non-human visitors
Cypress.io uses
Cypress

Test frontend behavior, requests to API endpoints, and assertions on JSON schemas for fixtures

Ataccama uses
Selenium

Selenium is a great way to automatically test if a build is sane and can be deployed.