mocha-parallel-tests vs StoryPlayer comparison of testing frameworks
What are the differences between mocha-parallel-tests and StoryPlayer?

	mocha-parallel-tests https://www.npmjs.com/package/mocha-parallel-tests	StoryPlayer http://datasift.github.io/storyplayer/
Programming language	JavaScript	PHP
Category	Unit Testing, Intergration Testing, End-to-End Testing	Unit testing, Functional Testing
General info	mocha-parallel-tests is a test runner for tests written with mocha testing framework. mocha-parallel-tests allows you to run your tests in parallel and executes each of your test files in a separate process while still maintaining the output of mocha	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
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	N/A	No
Client-side Allows testing code execution on the client, such as a web browser	Yes Mocha-parallel-tests Runs in the browser and is used widely to test front-end components and functionality. It can test various DOM elements, front-end functions and so on.	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
Server-side Allows testing the bahovior of a server-side code	Yes Mocha-parallel-tests provides convenient ways of testing the Node server.	Yes By writing a 'service story' which is a 'userstory' except it describes the behaviour of your back-end systems
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Mocha, which is the the framework which mocha-parallel-tests runs provides the hooks before(), after(), beforeEach(), and afterEach() to set up preconditions and clean up after your tests	Yes Storyplayer has fixtures that can create and destroy test environments on demand
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 Group fixtures are available	Yes It supports group fixtures
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	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.
Licence Licence type governing the use and redistribution of the software	MIT License	New BSD 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)	Provides Mocking capabilities through third party Libraries like sinon.js, simple-mock and nock	By using a library like mockery which intergrates well with storyplayer
Grouping Allows organizing tests in groups	Yes Grouping is supported and is accomplished by the using a nested 'describe()'	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework