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

	Hound https://github.com/HashNuke/hound	Cypress.io https://www.cypress.io/
Programming language	Elixir	JavaScript
Category	Browser Automation, Intergration Testing	End-to-End Testing, Intergration Testing, Unit Testing
General info	Elixir library for browser automation and writing intergration tests It is a front-end testing library that has support for: Selenium (Firefox, Chrome), ChromeDriver and PhantomJs. Also supports JavaScript applications and retries tests a few times before reporting errors	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 Allows for browser Automation and writing of end-to-end tests for web apps, supports Selenium WebDriver, ChromeDriver, and PhantomJS - GhostDriver	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
Server-side Allows testing the bahovior of a server-side code	N/A	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	N/A	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.	Yes Not inbuilt but by use of a third party library like ExopData	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 Yes, through the use of a third party library like Mockery	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	N/A	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