Alternatives to Cypress logo

Alternatives to Cypress

Selenium, TestCafe, Puppeteer, WebdriverIO, and Jest are the most popular alternatives and competitors to Cypress.
1.1K
1.3K
+ 1
88

What is Cypress and what are its top alternatives?

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.
Cypress is a tool in the Javascript Testing Framework category of a tech stack.
Cypress is an open source tool with 31.7K GitHub stars and 1.8K GitHub forks. Here鈥檚 a link to Cypress's open source repository on GitHub

Top Alternatives to Cypress

  • Selenium

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

  • TestCafe

    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

    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

    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

    Jest provides you with multiple layers on top of Jasmine.

  • Protractor

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

  • Juniper

    Juniper

    It provides high-performance networking & cybersecurity solutions to service providers, enterprise companies & public sector organizations. ...

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

Cypress alternatives & related posts

Selenium logo

Selenium

9.9K
7.4K
513
Web Browser Automation
9.9K
7.4K
+ 1
513
PROS OF SELENIUM
  • 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
CONS OF SELENIUM
  • 5
    Flaky tests
  • 1
    Slow as needs to make browser (even with no gui)

related Selenium posts

Kamil Kowalski
Lead Architect at Fresha | 27 upvotes 路 938.8K views

When you think about test automation, it鈥檚 crucial to make it everyone鈥檚 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
Benjamin Poon
QA Manager - Engineering at HBC Digital | 8 upvotes 路 670.2K views

For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

See more
TestCafe logo

TestCafe

111
177
17
A Node.js tool to automate end-to-end web testing
111
177
+ 1
17
PROS OF TESTCAFE
  • 3
    Open source
  • 3
    Cross-browser testing
  • 3
    Built in waits
  • 3
    Easy setup/installation
  • 2
    UI End to End testing
  • 2
    Supports Devices without extra software/package
  • 1
    Both client and server side debug
CONS OF TESTCAFE
  • 4
    No longer free

related TestCafe posts

Puppeteer logo

Puppeteer

305
422
21
Headless Chrome Node API
305
422
+ 1
21
PROS OF PUPPETEER
  • 8
    Scriptable web browser
  • 8
    Very well documented
  • 5
    Promise based
CONS OF PUPPETEER
  • 7
    Chrome only

related Puppeteer posts

Raziel Alron
Automation Engineer at Tipalti | 7 upvotes 路 72.5K views

Currently, we are using Protractor in our project. Since Protractor isn't updated anymore, we are looking for a new tool. The strongest suggestions are WebdriverIO or Puppeteer. Please help me figure out what tool would make the transition fastest and easiest. Please note that Protractor uses its own locator system, and we want the switch to be as simple as possible. Thank you!

See more

I work in a company building web apps with AngularJS. I started using Selenium for tests automation, as I am more familiar with Python. However, I found some difficulties, like the impossibility of using IDs and fixed lists of classes, ending up with using xpaths most, which unfortunately could change with fixes and modifications in the code.

So, I started using Puppeteer, but I am still learning. It seems easier to find elements on the webpage, even if the creation and managing of arrays of elements seem to be a little bit more complicated than in Selenium, but it could be also due to my poor knowledge of JavaScript.

Any comments on this comparison and also on comparisons with similar tools are welcome! :)

See more
WebdriverIO logo

WebdriverIO

187
307
35
Webdriver/Selenium 2.0 JavaScript bindings for Node.js
187
307
+ 1
35
PROS OF WEBDRIVERIO
  • 10
    Various integrations to vendors like Sauce Labs
  • 8
    Great community
  • 8
    Open Source
  • 7
    Easy to setup
  • 2
    Best solution for broad browser support
CONS OF WEBDRIVERIO
  • 6
    High maintenance

related WebdriverIO posts

Raziel Alron
Automation Engineer at Tipalti | 7 upvotes 路 72.5K views

Currently, we are using Protractor in our project. Since Protractor isn't updated anymore, we are looking for a new tool. The strongest suggestions are WebdriverIO or Puppeteer. Please help me figure out what tool would make the transition fastest and easiest. Please note that Protractor uses its own locator system, and we want the switch to be as simple as possible. Thank you!

See more
Kevin Roulleau
QA Engineer Freelance at happn | 5 upvotes 路 150.4K views

I chose WebdriverIO and Appium to implement a E2E tests solution on a native mobile app. WebdriverIO goes well beyond just implementing the Selenium / Appium protocol and allows to run tests in parallel out of the box. Appium has the big advantage of supporting iOS and Android platforms, so the test codebase and tools are exactly the same, which greatly reduces the learning curve and implementation time.

See more
Jest logo

Jest

3.4K
2.3K
161
Painless JavaScript Unit Testing
3.4K
2.3K
+ 1
161
PROS OF JEST
  • 33
    Open source
  • 30
    Mock by default makes testing much simpler
  • 21
    Testing React Native Apps
  • 18
    Parallel test running
  • 14
    Fast
  • 13
    Bundled with JSDOM to enable DOM testing
  • 7
    Mock by default screws up your classes, breaking tests
  • 7
    Out of the box code coverage
  • 6
    One stop shop for unit testing
  • 6
    Promise support
  • 3
    Great documentation
  • 1
    Built in watch option with interactive filtering menu
  • 1
    Preset support
  • 1
    Assert Library Included
  • 0
    Can be used for BDD
CONS OF JEST
  • 2
    Many bugs still not fixed months/years after reporting
  • 2
    Multiple error messages for same error
  • 2
    Documentation
  • 2
    Ambiguous configuration
  • 1
    Bugged
  • 1
    Unstable
  • 1
    Bad docs
  • 1
    Ambiguous
  • 1
    Still does't support .mjs files natively
  • 1
    Can't fail beforeAll to abort tests
  • 1
    Difficult to run single test/describe/file
  • 1
    Meh
  • 1
    Difficult
  • 1
    BeforeAll timing out makes all passing tests fail
  • 1
    Reporter is too general
  • 0
    Interaction with watch mode on terminal

related Jest posts

Robert Zuber

We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

See more
Shared insights
on
Cypress
Jest

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
Protractor logo

Protractor

478
411
21
End-to-end test framework for Angular and AngularJS applications
478
411
+ 1
21
PROS OF PROTRACTOR
  • 7
    Easy setup
  • 6
    Quick tests implementation
  • 3
    Promise support
  • 3
    Open source
  • 2
    Flexible
CONS OF PROTRACTOR
  • 3
    Limited

related Protractor posts

Raziel Alron
Automation Engineer at Tipalti | 7 upvotes 路 72.5K views

Currently, we are using Protractor in our project. Since Protractor isn't updated anymore, we are looking for a new tool. The strongest suggestions are WebdriverIO or Puppeteer. Please help me figure out what tool would make the transition fastest and easiest. Please note that Protractor uses its own locator system, and we want the switch to be as simple as possible. Thank you!

See more
Juniper logo

Juniper

9
8
0
High-performance networking & cybersecurity solutions
9
8
+ 1
0
PROS OF JUNIPER
    Be the first to leave a pro
    CONS OF JUNIPER
      Be the first to leave a con

      related Juniper posts

      Mocha logo

      Mocha

      3.5K
      2.5K
      425
      Simple, flexible, fun javascript test framework for node.js & the browser
      3.5K
      2.5K
      + 1
      425
      PROS OF MOCHA
      • 136
        Open source
      • 100
        Simple
      • 81
        Promise support
      • 48
        Flexible
      • 28
        Easy to add support for Generators
      • 12
        For browser and server testing
      • 7
        Curstom assertion libraries
      • 4
        Works with Karma
      • 3
        No other better tools
      • 1
        Simple integration testing
      • 1
        Default reporter is nice, clean, and itemized
      • 1
        Simple setup
      • 1
        Works with saucelabs
      • 1
        Lots of tutorials and help online
      • 1
        Works with BrowserStack
      CONS OF MOCHA
      • 3
        Cannot test a promisified functions without assertion
      • 1
        Not as many reporter options as Jest
      • 1
        No assertion count in results

      related Mocha posts

      I use both mocha and Jest because:

      • I don't care whether teams use Jest or Mocha. But jest is way too overhyped. Most devs are writing integration tests and think that it's so much better but frankly I don't write integration tests as the way to get both design feedback and confidence when I code. I adhere to the test pyramid, not ice cream cone or the dumb "trophy"

      • I TDD, so I only ever use the "API" of test frameworks. I don't do a lot of integration tests for TDD and all the bells and whistles Jest provides you from the command-line I just don't need. And I certainly do not care about or touch Jest Snapshots, I despise them

      • My tests are fast enough because I write isolated tests with TDD, so I don't run into performance issues. Example: I write my tests in a way that I can run 300 tests in literally 1 second with mocha. So the Jest ability to pinpoint and only run those tests which are affected by code changes. I want to run all of them every time when I TDD. It's a different mindset when you TDD

      • I also mainly code in IntelliJ or WebStorm because I feel the tools in that IDE far surpass VSCode and I also love running the test UI runner in it vs. lousy command-line

      • I feel both mocha and Jest read just fine in terms of code readability. Jest might have shorter assertion syntax but I don't really care. I just care that I can read the damn test and my tests are written well and my test descriptions, as well as the code itself including constants represent business language, not technical. I care most about BDD, clean code, 4 rules of simple design, and SOLID

      • I don't like using mock frameworks so no I don't use Jest's Mocking framework. I don't have to mock a lot in my tests due to the nature of how I strive to code...I keep my design simple and modular using principals such as clean code and 4 rules of simple design. If I must mock, I create very simple custom mocks with JS

      • On the contrary to the belief that integration tests and mount are the way to go (this belief drives me absolutely crazy, especially Dodd's promoting that), I TDD with shallow & enzyme. My tests are simple. My design is driven by my tests and my tests give me quick and useful feedback. I have a course I'm working on coming out soon on TDD with React to show you how to truly test the FE and why the ice cream cone and trophy suck (you're being scammed people). Watch for that here: https://twitter.com/DaveSchinkel/status/1062267649235791873

      Don't forget to upvote this post!

      Mocha Jest JavaScript React @jsdom Enzyme #tdd #bdd #testdrivendevelopment

      See more
      Jack Graves
      Head of Product Development at Automation Consultants | 3 upvotes 路 108.4K views

      We use JUnit and Jest to perform the bulk of our automated test scenarios, with additional work with Apache JMeter for performance testing - for example, the Atlassian Data Center compliance testing is performed with JMeter. Jest provides testing for the React interfaces, which make up the backend of our App offerings. JUnit is used for Unit Testing our Server-based Apps. Mocha is another tool we use.

      See more