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

Testify

https://github.com/Yelp/Testify

StoryPlayer

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

Python

PHP

Category

Unit Testing

Unit testing, Functional Testing

General info

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

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 functionality and behaviour can be tested by Testify.

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

Testify can test various server and database behaviours and functionality

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

Fixture methods are supported and it follows a decorator based approach, that is they are written similar to decorators

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

Group fixtures are supported

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.

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.

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

Apache License 2.0

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

It includes the turtle mock object library

By using a library like mockery which intergrates well with storyplayer
Grouping
Allows organizing tests in groups

Yes

Testify includes support for detecting and running test suites, grouped by modules, classes, or individual test methods.

Yes

Storyplayer’s job is to execute a suite of functional tests
Other
Other useful information about the testing framework