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

	StoryPlayer http://datasift.github.io/storyplayer/	Testify https://github.com/Yelp/Testify
Programming language	PHP	Python
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	A Python unit testing framework modelled after unittest Testify is modelled after unittest but has more features while still supporting unittest classes. It has more pythonic naming conventions, an better test runner output visually, a decorator-based approach to fixture methods among many other features
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 functionality and behaviour can be tested by Testify.
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 Testify can test various server and database behaviours 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 Fixture methods are supported and it follows a decorator based approach, that is they are written similar to decorators
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 Group fixtures are supported
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 One can create generator methods to yield runnable test methods which will pick out the test methods from your TestCases, and then exclude any in any of your exclude_suites method.If there are any require_suites, it will then further limit itself to test methods in those suites.
Licence Licence type governing the use and redistribution of the software	New BSD License	Apache License 2.0
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 includes the turtle mock object library
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	Yes Testify includes support for detecting and running test suites, grouped by modules, classes, or individual test methods.
Other Other useful information about the testing framework