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

	StoryPlayer http://datasift.github.io/storyplayer/	Goconvey https://github.com/smartystreets/goconvey
Programming language	PHP	Go
Category	Unit testing, Functional Testing	Regression 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	BDD style testing framework for Go Goconvey is a two pronged testing tool consisting of a test runner that watches your code for changes, runs 'go test' and renders your results in a web browser and the second a library that allows you to write BDD-style tests with standard 'go test' functions
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, Goconvey can perform front-end tests
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 one can perform end-to-end HTTP tests with goconvey to see how an application works against remote servers
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 Yes, Goconvey uses scopes to define fixtures and a reset function for teardown
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 One can define group fixtures using scopes
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 The web UI has a button to open the built in generator
Licence Licence type governing the use and redistribution of the software	New BSD License	Goconvey 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 Using the mock package or mockery library to autogenerate mock code
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	Yes Similar to a table driven approach an entire suite can be contained in a single function
Other Other useful information about the testing framework