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

	StoryPlayer http://datasift.github.io/storyplayer/	unittest2 https://pypi.org/project/unittest2/
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	Unittest2 is a newer version on the inbuilt unit testing framework unittest To use o use unittest2 instead of unittest, simply replace 'import unittest' with 'import unittest2'. It has many new features such as: - addCleanups for better resource management; -many new assert methods; - assertRaises as context manager, with access to the exception afterwards; - test discovery and new command line options (including failfast and better handling of ctrl-C during test runs); - class and module level fixtures: setUpClass, tearDownClass, setUpModule, tearDownModule; -test skipping and expected failures and many more improvements on the API and bug fixes
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes unittest2 is a newer version of unittest which is an xUnit style framework for Python.
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 unittest2. function by function
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 We can write tests with unittest2 to test each function for server-side behaviour
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 By use of the 'setUp()' function which is called to prepare the test fixture
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 unittest2 allows you to group your initialization code buy use of the 'setUp()' function and clean up code with a 'tearDown()' function
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 unittest2 contains generator methods in the module 'unittest.TestCase'
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 Mocks are available from the library unittest.mock which allows you to replace parts of your system under test with mock objects
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	Yes One can build suites either manually or use test discovery to build the suite automatically by scanning a directory
Other Other useful information about the testing framework