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

	TwistedTrial https://twistedmatrix.com/trac/wiki/TwistedTrial	StoryPlayer http://datasift.github.io/storyplayer/
Programming language	Python	PHP
Category	Unit Testing, unittest Extensions	Unit testing, Functional Testing
General info	Trial is a unit testing framework for Python built by Twisted Matrix labs Trial is composed of two parts: First is a command-line test runner, which can be run on plain Python unit tests and can do automated unit-test discovery across files, modules, or even arbitrarily nested packages. Second is a test library, derived from Python's 'unittest.TestCase'	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.	No	No
Client-side Allows testing code execution on the client, such as a web browser	Yes Front-end components can be tested for example adding a web front-end using simple twisted.web.resource.Resource objects	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 Server-side behaviour can be tested with Trial, it has various functions for this in the twisted.web.Resource package	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	Yes Trial supports various fixture methods such as 'setUp()' and 'tearDown' functions fixture for normal semantics of setup, and teardown	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 Methods like 'setUp()' allow for creation of group fixtures	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.	Through use of third party libraries like test-generator.	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)	Yes Trial can access the mock library inbuilt in python for mocking purposes	By using a library like mockery which intergrates well with storyplayer
Grouping Allows organizing tests in groups	Yes Trial allows tests to be grouped into test packages	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework