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

Jasmine

https://github.com/jasmine/jasmine

Cypress.io

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

JavaScript

JavaScript

Category

Unit Testing, End-to-End Testing

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

General info

JS Unit test framework, BDD based for Node.JS applications used with Angular.JS web applications and also paired with 'Karma' task runner

It's a BDD (Behavior Driven Development) test framework for JavaScript especially designed for manual QAs to understand the automation tests. It does not depend on the any JavaScript framework or browser. So it's very well suited for Node.js projects and websites

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

Jasmine works well in and with browsers to test client-side components and functionality

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

Jasmine works with NodeJs to test its back-end components and behaviour

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

By using 'jasmine-fixture' which can help write specs that interact with the DOM making it easier to injectHTML fixtures

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.

N/A

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.

N/A

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)

By using a a plugin called jasmine-ajax that allows ajax calls to be mocked out in tests

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

Yes

Using the describe function which is for grouping related tests, typically each test file has one at the top level.

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