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

StoryPlayer

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

Tape

https://github.com/substack/tape
Programming language

PHP

JavaScript

Category

Unit testing, Functional Testing

Unit Testing, Intergration 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

tap-producing test harness for node and browsers.

Tape API is a small superset of the node core assert module
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

Yes

It does support xUnit output
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

You can write tests for any part of your front-end code to test any component or functionality
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

With tape you can test any back-end component, behaviour and functionality after all it supports TAP (Test Anything Protocol)
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

No

Tape contains only the essential features for making assertions on your code but there is a package called redtape that extends tape to give you beforeEach and afterEach functionality
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

No

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.

No

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

No

Tape is a minimalistic framework that provides only essential features to make your assertions about your code
Grouping
Allows organizing tests in groups

Yes

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

No

Tape contains only the essential features for making assertions on your code
Other
Other useful information about the testing framework