StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Testing Frameworks
  4. Browser Testing
  5. Cypress vs Selenium

Cypress vs Selenium

OverviewDecisionsComparisonAlternatives

Overview

Selenium
Selenium
Stacks16.2K
Followers12.6K
Votes527
GitHub Stars33.6K
Forks8.6K
Cypress
Cypress
Stacks3.5K
Followers2.0K
Votes115
GitHub Stars49.4K
Forks3.4K

Cypress vs Selenium: What are the differences?

Introduction: Cypress and Selenium are both popular testing frameworks used for automating web applications. However, they differ in several key aspects.

  1. Installation and Setup: Cypress provides a simple installation process by simply running a single command, while Selenium requires downloading and setting up different components like the WebDriver and language-specific bindings separately.

  2. API and Syntax: Cypress has its own API designed specifically for modern web applications, offering commands to interact with elements and control network requests. Selenium, on the other hand, uses a WebDriver API which requires developers to have a better understanding of the underlying technologies like XPath or CSS selectors.

  3. Execution Speed: Cypress has the advantage of executing tests directly within the browser, allowing it to operate faster than Selenium. While Selenium performs actions by sending requests to the WebDriver and receiving responses, Cypress runs directly in the browser itself, eliminating the overhead of network requests.

  4. Debugging Capabilities: Cypress provides better debugging capabilities than Selenium with its real-time reloading and interactive debugging tools. Developers can easily pause and inspect the state of the application during test execution. Selenium lacks these features, making debugging more challenging.

  5. Automatic Retries: Cypress has an automatic retry mechanism built-in, which means it automatically retries failed assertions and commands until they pass or reach a maximum limit. Selenium does not have this feature, making it less convenient to handle flaky tests.

  6. Cross-Browser Testing: Selenium is known for its cross-browser compatibility, as it supports major browsers like Chrome, Firefox, Safari, and Internet Explorer. Cypress, on the other hand, currently only supports Chrome and Electron browsers, limiting its cross-browser testing capabilities.

In summary, Cypress offers a simpler and faster setup, provides a modern API with built-in debugging capabilities and automatic retries. However, it lacks comprehensive cross-browser support compared to Selenium.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Selenium, Cypress

Kamil
Kamil

Lead Architect at Fresha

Dec 23, 2019

DecidedonSeleniumSeleniumJavaJavaRubyRuby

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.

4.17M views4.17M
Comments
Dane
Dane

Feb 7, 2020

Needs adviceonCypressCypressJestJest

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.

836k views836k
Comments
Yildiz
Yildiz

testmanager/automation tester at medicalservice

May 12, 2020

Needs adviceonAngularJSAngularJSTypeScriptTypeScriptCypressCypress

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...

277k views277k
Comments

Detailed Comparison

Selenium
Selenium
Cypress
Cypress

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 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.

-
Time Travel; Debuggability; Automatic Waiting; Spies, Stubs, and Clocks; Network Traffic Control; Consistent Results; Screenshots and Videos
Statistics
GitHub Stars
33.6K
GitHub Stars
49.4K
GitHub Forks
8.6K
GitHub Forks
3.4K
Stacks
16.2K
Stacks
3.5K
Followers
12.6K
Followers
2.0K
Votes
527
Votes
115
Pros & Cons
Pros
  • 177
    Automates browsers
  • 154
    Testing
  • 101
    Essential tool for running test automation
  • 24
    Remote Control
  • 24
    Record-Playback
Cons
  • 8
    Flaky tests
  • 4
    Slow as needs to make browser (even with no gui)
  • 2
    Update browser drivers
Pros
  • 29
    Open source
  • 22
    Great documentation
  • 20
    Simple usage
  • 18
    Fast
  • 10
    Cross Browser testing
Cons
  • 21
    Cypress is weak at cross-browser testing
  • 14
    Switch tabs : Cypress can'nt support
  • 12
    No iFrame support
  • 9
    No page object support
  • 9
    No multiple domain support

What are some alternatives to Selenium, Cypress?

BrowserStack

BrowserStack

BrowserStack is the leading test platform built for developers & QAs to expand test coverage, scale & optimize testing with cross-browser, real device cloud, accessibility, visual testing, test management, and test observability.

Sauce Labs

Sauce Labs

Cloud-based automated testing platform enables developers and QEs to perform functional, JavaScript unit, and manual tests with Selenium or Appium on web and mobile apps. Videos and screenshots for easy debugging. Secure and CI-ready.

Mocha

Mocha

Mocha is a feature-rich JavaScript test framework running on node.js and the browser, making asynchronous testing simple and fun. Mocha tests run serially, allowing for flexible and accurate reporting, while mapping uncaught exceptions to the correct test cases.

LambdaTest

LambdaTest

LambdaTest platform provides secure, scalable and insightful test orchestration for website, and mobile app testing. Customers at different points in their DevOps lifecycle can leverage Automation and/or Manual testing on LambdaTest.

Jasmine

Jasmine

Jasmine is a Behavior Driven Development testing framework for JavaScript. It does not rely on browsers, DOM, or any JavaScript framework. Thus it's suited for websites, Node.js projects, or anywhere that JavaScript can run.

Karma

Karma

Karma is not a testing framework, nor an assertion library. Karma just launches a HTTP server, and generates the test runner HTML file you probably already know from your favourite testing framework. So for testing purposes you can use pretty much anything you like.

Jest

Jest

Jest provides you with multiple layers on top of Jasmine.

Playwright

Playwright

It is a Node library to automate the Chromium, WebKit and Firefox browsers with a single API. It enables cross-browser web automation that is ever-green, capable, reliable and fast.

Rainforest QA

Rainforest QA

Rainforest gives you the reliability of a QA team and the speed of automation, without the hassle of managing a team or the pain of writing automated tests.

CodeceptJS

CodeceptJS

It is a modern end to end testing framework with a special BDD-style syntax. The test is written as a linear scenario of user's action on a site. Each test is described inside a Scenario function with I object passed into it.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana