Knapsack Pro

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

StoryPlayer

http://datasift.github.io/storyplayer/

unittest

https://docs.Python.org/3/library/unittest.html
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

unittest is a unit testing framework for Python

The unittest test framework is Python’s xUnit style framework. It is a standard module that is bundled with Python and supports the automation and aggregation of tests and common setup and shutdown code for them.
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

Yes

unittest is a xUnit style frameworkfor Python, it was previously called PyUnit.
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 unittest.
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

Since the webserver funtionalities have their own features and each feature has its own functions, we can write tests with unittest to test each function
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

unittest allows you to group your initialization code into a setUp function and clean up code in 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

unittest 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