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

StoryPlayer

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

TestOOB

https://pypi.org/project/testoob/
Programming language

PHP

Python

Category

Unit testing, Functional Testing

Unit Testing, unittest Extensions

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

Testoob is an advanced unit testing framework for Python.

Testoob integrates with existing unittest test suites. It contains many features like: a filter which tests to run with regular expressions, output test results as XML/HTML/PDF, test skipping, color output on a terminal and more.
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

Testoob can test front-end features since it is a unit testing tool. One can write a test for each function that is on the client side
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

Testoob can test back-end functionality since it is a unit testing tool. One can write a test for each function in the back-end.
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

TestOOB extends unittest and prepares fixtures by use of the 'setUp() function just like unittest
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

The 'setUp()' function allows you to group your initialization functions
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

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

Mocks are available - testoob can acess library unittest.mock which is used for mocking
Grouping
Allows organizing tests in groups

Yes

Storyplayer’s job is to execute a suite of functional tests

Yes

One can build suites with testoob
Other
Other useful information about the testing framework