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

	StoryPlayer http://datasift.github.io/storyplayer/	WebdriverIO https://webdriver.io/
Programming language	PHP	JavaScript
Category	Unit testing, Functional Testing	Browser Automation, Unit Testing, Functional 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	WebdriverIO is the next-gen WebDriver test framework for Node.js made upon Selenium WebdriverIO is written in JavaScript and uses Selenium under the hood. It also comes with its own inbuilt test runner and supports other testing frameworks like Jasmine, Cucumber, and Mocha
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes
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 WebdriverIO allows the use of advanced CSS selectors and makes it easy to find elements for front-end testing
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 It can be used to test server side 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	Yes WebdriverIO supports the creation of fixtures
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	Yes WebdriverIO supports the creation of 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.	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	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 It contains a mocking service called 'wdio-wiremock-service'
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	Yes WebdriverIO allows one to build test suites, you can run these test in parallel and organize them by adjusting the 'maxInstances' property in your config file
Other Other useful information about the testing framework