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

	StoryPlayer http://datasift.github.io/storyplayer/	Peridot http://peridot-php.github.io/
Programming language	PHP	PHP
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	Peridot is a lightweight, extensible testing framework for PHP It features an event-driven architecture that allows testers to easily customize the framework via plugins and reporters, and uses the 'describe-it', syntax making the testing language clear and readable
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 Front-end components can be tested with Peridot
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 Back-end componets and behaviours can be tested as small units
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 Peridot has several methods that allow one to create and define 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 There are methods to create group fixtures in Peridot
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	Peridot does not include mocking out of the box but there are some great tools like 'Mockery' and 'Prophecy' which Peridot intergrates very well with
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	Yes By use of describe and context blocks and it has a Runner which is responsible for running a given Suite.
Other Other useful information about the testing framework