Cucumber vs Cypress.io comparison of testing frameworks
What are the differences between Cucumber and Cypress.io?

Cucumber

https://github.com/cucumber/cucumber-ruby

Cypress.io

https://www.cypress.io/
Programming language

Ruby

JavaScript

Category

Acceptance Testing

End-to-End Testing, Intergration Testing, Unit Testing

General info

An automation tool for Behavior-Driven Development

The specifications are written in plain texts, which allows them to be easily understandable for all stakeholders. Cucumber Framework also supports languages beyond Ruby e.g. Java, JavaScript and Scala.

Cypress users are typically developers or QA engineers building web applications using modern JavaScript frameworks. This is the top tier UI automation framework which outsmarts Selenium based frameworks in most of the aspects!

Cypress enables you to write all types of tests: 1. End-to-end tests; 2. Integration tests; 3. Unit tests; 4. Cypress can test anything that runs in a browser; Apart from that Cypress provides the Dashboard facility for CI/CD
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

You can test the front-end part like the GUI using cucumber and selenium, they integrate well to test your front-end.

Yes

This is the primary goal of Cypress, it tests anything that runs in a browser and works to build great user experience that is it tests the applications flow from beginning to end from a user perspective. It is built to handle modern JavaScript frameworks especially well and also works equally well on older server rendered pages or applications
Server-side
Allows testing the bahovior of a server-side code

Yes

You can test back-end components such as APIs using rest & soap clients, and databases using whatever client libraries were provided by the libraries that existed in those stacks

Yes

Although Cypress is not a general automation framework, nor is it a unit testing framework for your back-end services, It can test back-end behaviours for example using cy.task() command which provides a way for running Node code, so you can take actions necessary for your tests outside of the scope of Cypress
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

Yes

Cypress has inbuilt fixtures capabilities or example using the command 'cy.fixture(filePath)' loads a fixed set of data located in a file
Group fixtures
Allows defining a fixed, specific states of data for a group of tests (group-fixtures). This ensures specific environment for a given group of tests.

Yes

Using the cucumber extension aruba you can create fixures in two steps: 1.Create a fixtures-directory; 2.Create fixture files in this directory

Yes

Cypress can create group fixtures using the 'cy.fixture' command
Generators
Supports data generators for tests. Data generators generate input data for test. The test is then run for each input data produced in this way.

Yes

You can group your fixtures inside your fixtures directories

N/A

Licence
Licence type governing the use and redistribution of the software

MIT License

MIT License

Mocks
Mocks are objects that simulate the behavior of real objects. Using mocks allows testing some part of the code in isolation (with other parts mocked when needed)

Yes

By using all of RSpec’s supported mocking frameworks (RSpec, Mocha, RR, Flexmock)

Yes

Cypress comes built in with the ability to stub and spy with cy.stub(), cy.spy(), It also automatically bundles 'sinon', 'lolex' and 'sinon-chai' which all work to give Cypress mocking capabilities
Grouping
Allows organizing tests in groups

No

Yes

Cypress allows you to configure tests into groups however there is no way currently to run the groups
Other
Other useful information about the testing framework