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

	Cypress.io https://www.cypress.io/	wru https://github.com/WebReflection/wru
Programming language	JavaScript	JavaScript
Category	End-to-End Testing, Intergration Testing, Unit Testing	Unit Testing
General info	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	wru is an essential general purpose test framework compatible with web environment, node.js, Rhino, and now PhantomJS too. wru is compatible with basically all possible browsers out there included IE5.5, IE6, IE7, IE8, IE9, IE10, Chrome, Firefox, Safari, Webkit based, Mobile Browsers, and Opera. On server side wru is compatible with latest node.js, Rhino, PhantomJS, and JavaScriptCore versions.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes Wru is compatible with xUnit
Client-side Allows testing code execution on the client, such as a web browser	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's perspective. It is built to handle modern JavaScript frameworks especially well and also works equally well on older server rendered pages or applications	Yes Wru tests front-end components and functions, it is compatible with HTML and runs on probably all browsers
Server-side Allows testing the bahovior of a server-side code	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	Yes It is used to test back-end components and behaviour and runs in server environments
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	N/A
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 Cypress can create group fixtures using the 'cy.fixture' command	N/A
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)	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	You can implement your stubs and mocks using a wru.assert(...) when necessary during a specific test.
Grouping Allows organizing tests in groups	Yes Cypress allows you to configure tests into groups however there is no way currently to run the groups	N/A
Other Other useful information about the testing framework