StoryPlayer vs Hound comparison of testing frameworks
What are the differences between StoryPlayer and Hound?

	StoryPlayer http://datasift.github.io/storyplayer/	Hound https://github.com/HashNuke/hound
Programming language	PHP	Elixir
Category	Unit testing, Functional Testing	Browser Automation, Intergration Testing
General info	Storyplayer is a full-stack testing framework Storyplayer follows a TDD testing approach and makes it possible to write end-to-end tests for an entire platform. It has support for creating and destroying test environments on demand	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
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 By running a 'user story' which is a simple statement that describes one action, and who can perform that action then record of the conversations about this action, this is how you would test front-end functionality and components	Yes Allows for browser Automation and writing of end-to-end tests for web apps, supports Selenium WebDriver, ChromeDriver, and PhantomJS - GhostDriver
Server-side Allows testing the bahovior of a server-side code	Yes By writing a 'service story' which is a 'userstory' except it describes the behaviour of your back-end systems	N/A
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes Storyplayer has fixtures that can create and destroy test environments on demand	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 It supports group fixtures	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.	Yes foreach(hostWithRole()) is a generator allows you to easily perform actions against all hosts in your test environment without having to hard-code the host IDs or hostnames into your story.	Yes Not inbuilt but by use of a third party library like ExopData
Licence Licence type governing the use and redistribution of the software	New BSD 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 library like mockery which intergrates well with storyplayer	Yes Yes, through the use of a third party library like Mockery
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	N/A
Other Other useful information about the testing framework