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

StoryPlayer

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

Ginkgo

http://onsi.github.io/ginkgo/
Programming language

PHP

Go

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

BDD testing framework for Go

Ginkgo is a BDD testing framework for Go that has a great matcher library to go with it called Gomega and intergrates with the standard testing library
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

Yes, by creating unit tests then testing individual front-end components
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

Yes by creating unit tests then testing various back-end components
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

N/A

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

N/A

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

They are available by running the command: 'ginko bootstrap'
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

Dvelopers can generate mocks by using the third party package 'gomock'
Grouping
Allows organizing tests in groups

Yes

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

Yes

Ginkgo allows you to group tests in 'Describe' and 'Context' container blocks. It also provides 'It' and 'Specify' blocks to hold your assertions
Other
Other useful information about the testing framework