Cypress is a modern JavaScript-based end-to-end testing framework that doesn't use Selenium. As with most testing frameworks, Cypress has its critics and super fans. Read an earlier blog post about the pros and cons of Cypress if you'd like to get up to speed about why you might want to use it or not.

Many companies are choosing to use Cypress to write their end-to-end tests instead of Selenium.  Cypress offers a Dashboard Service that you can pay for to run and debug your tests. Testery's continuous testing platform also provides the capability to run and debug your Cypress tests.  Here are 5 benefits to running your Cypress tests on Testery versus Cypress' Dashboard Service.

  1. High parallelization without managing servers.  You can parallelize your tests using the Cypress Dashboard but you have to depend on your CI spinning up a new server for each parallel test.  You will have to manage those yourself and make sure your CI doesn't have limits on number of parallel tests you can run.  Most do have limits and you pay as you add parallel resources.
    With Testery, you don't have to worry about managing infrastructure.  Testery scales as you need to grow with no limits to parallelization and you only pay for what you use.
  2. Filtering your tests using tags. Cypress does not support tagging so you are not able to filter your tests based on tags when running tests on Cypress.  This is a useful feature when you want to run a subset of tests on a given environment.  Testery supports using tags when running your Cypress tests.  You can use mocha or cucumber tags, specify which tags you want to run in Testery and voila!
  3. File or test based parallelization strategy.  Running your tests in parallel can save you tons of time compared to running all your tests on a single machine.  Running tests in parallel enables your team to improve your continuous testing and delivery process. Cypress only supports file based parallelization meaning your tests have to be split into multiple files in order to be run in parallel.  Testery supports both file and test based parallelization.  For instance, you can have a single file with 100 tests and have the tests within that file in parallel.
  4. Rerunning tests within a file. Testery allows you to rerun a single test within a file which helps during the debugging process.  With Cypress, you would have to rerun the entire file.
  5. Running all test types in the same place.  Most companies are writing multiple kinds of tests to ensure their applications are tested appropriately.  This includes a mix of integration, API, UI, database, regression, e2e, etc. The Testery platform supports all types of tests making it easy to see results in a single place. Other tools out there tend to favor a single type of test.

Testery's continuous testing platform was created to help teams run tests easier, faster and at scale.  Cypress is one of the many frameworks Testery supports.  It hooks into any CI/CD.  Try it out today!