Cypress has an easier onboarding than other frameworks. With Cypress NPM, you can simply install with a single command. You get all the screenshots and video by default on every CI, on every platform. You can now run Cypress tests on the Testery continuous testing platform. Here's an example of how to configure Tugboat to run Cypress tests on Testery, but you can also configure from any CI.
More and more companies are switching to developer-led testing and analyzing if their existing testing framework is the right one for their tech stack and organization. For years, Selenium WebDriver has been the de facto standard when it comes to UI test automation. However, a quick npm search for Cypress shows the increasing popularity of Cypress. It also has a great active community that can be found here.
This post is unbiased and lists some pros and cons of using Cypress. There are a few references to Selenium in this post too because the question “Cypress or Selenium?” often comes up. These comments are also meant to be unbiased. If you want to learn some more details of the pros of Cypress, here is a fairly recent article written by a Cypress Ambassador that promotes why you might want to use it.
Pro: Cypress can run recorded tests in parallel across multiple virtual machines since version 3.1.0. You just pass in a --parallel flag and spin up multiple machines on your CI provider and Cypress will automatically load balance all of your specs.
Con: Parallel tests can technically run on a single machine, but Cypress does not recommend it since the machine would require significant resources to run your tests efficiently. You will also need to manage and maintain the machines you spin up on your CI. Beware of the pricing if taking this approach as it can get expensive to run multiple machines and some CI’s have a maximum number they will support. (For a different approach, check out running your tests on Testery so you don’t have to manage or maintain your testing infrastructure.)
Pro: Until Spring of 2020, Cypress only supported Chrome. However, with a recent release, Cypress started supporting Firefox and Edge as well. Now companies can do some cross browser testing with Cypress. Chrome is the most popular browser so Cypress covers +70% of the market between Chrome, Firefox and Edge. Here is a list of the current browsers Cypress supports.
Con: Cypress doesn’t support any other browsers such as IE, Safari, or Opera. If you have a requirement ensuring that your web apps run smoothly across all browsers Cypress may not be a good option for you. Here’s a blog post where Testery talks about if cross browser testing is necessary.
Pro: Don’t need mobile testing? Perfect...because Cypress doesn’t support mobile testing.
Con: Cypress doesn’t support mobile testing so you will need another testing solution if you have this requirement.
Pro: Cypress has a built-in mechanism that handles waiting for DOM elements (there is a maximum waiting time setting that defaults to 10,000 ms). This means features like sleep or wait are not necessary. It also eliminates a few selenium webdriver errors/exceptions caused by dynamic page content. The result is more stable tests that run faster. It also has built-in retries. Modern web applications are continually updating themselves, and they're a little unpredictable. These all make Cypress less flaky.
Con: A few things that developers are having to find hacks to deal with are: navigating to a URL command is flaky, no shadow DOM support, working with iframes is a huge pain, can’t work with more than one tab, and can’t navigate to a different domain URL (in case you want to test third party apps in your workflow).
Native Event Handling
Pro: Cypress states that support for native event handling is on their roadmap.
Con: Cypress does not handle all native events as it uses synthetic events. This makes it difficult to test certain things. Events such as file upload, hover and scroll are not supported yet. For an updated status of what is supported follow this ticket.
Pro: Cypress support interacting with an API for end-to-end testing. There is a built in api testing library that’s simple/easy to use. This is something selenium/WebDriver.io can’t do without using a different library and extending the framework.
Con: If you are just testing an API there is no need for a browser. Cypress is always running a browser so it may not feel natural.
Time Travel and Debuggability
Pro: Cypress gives you the ability to travel back in time to each command's snapshot like "cy.contains". So, you are able to see what happens before or after some action in a specific command, and it highlights the element and scrolls it into the top of the page displayed in preview.
Cypress provides a good debugging tool that you can check easily why your tests are failing. Your Cypress code runs in the same run loop as your application. It automatically reloads when you make any change to your tests. You have full access to code while the code is running on the page.
Check your facts before selecting any test automation tool as there are nuances to every tool. Frameworks and platforms change and evolve over time. There are many variables to check if a specific framework such as Cypress would be a good fit for your project. If you have time, writing a Proof of Concept (PoC) is a good way to start.
Need help deciding if Cypress is a fit for your team? Need to automate running Cypress tests? Testery would be glad to guide you. Let us help you down your test automation journey.
Special thanks to Pedro Hyvo for help writing this blog post. His experience with Cypress was invaluable. Pedro works for Modus Create as a QA consultant. Modus Create helps companies accelerate their response with digital disruption with product strategy, digital product design/build, user experience, and process change consulting.