StoryPlayer vs Wallaby.js comparison of testing frameworks
What are the differences between StoryPlayer and Wallaby.js?

	StoryPlayer http://datasift.github.io/storyplayer/	Wallaby.js https://wallabyjs.com/
Programming language	PHP	JavaScript
Category	Unit testing, Functional Testing	Unit 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	Wallaby.js is an integrated continuous testing tool for JavaScript. Wallaby.js runs your tests immediately as you change your code (you don’t even have to save the file) and reports code coverage and other results directly to your code editor. Its also uses various techniques such as dependency analysis to only execute tests affected by your code changes and parallel test execution to ensure your tests run as fast as possible.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	N/A
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 Wallaby.js can test front-end components and functionality
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	Yes Wallaby.js can test server behaviour and functionality
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.	N/A
Licence Licence type governing the use and redistribution of the software	New BSD License	N/A
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	By use of a third party library Jest works well with wallaby
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework