go test/testing vs StoryPlayer comparison of testing frameworks
What are the differences between go test/testing and StoryPlayer?

go test/testing

https://golang.org/pkg/testing/

StoryPlayer

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

Go

PHP

Category

Unit Testing

Unit testing, Functional Testing

General info

go test is an inbuilt tool/command for conducting automated tests in Golang while testing is the inbuilt testing library

Testing is the package that is shipped with go and combines with the go test command to provide a minimal but complete testing experience

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

However there are Plugins such as https://github.com/tebeka/go2xunitto convert the output of Go testing library into xUnit format

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

Yes it can be used effectively for front-end testing

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

Yes, it is used by developers for end-to-end testing so the back-end can be tested easily as well

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

Yes it's straightforward in that first when you run 'go test' for packages in the scope the test will be executed with its working directory set to the source directory of the package being tested. Second the 'go test' tool will ignore any directory in your $GOPATH that starts with the word 'testdata' , starts with a period or an underscore

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 can be done following a similar procedure as a single fixture

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

They are available by importing a package called 'gotests' (https://github.com/cweill/gotests)

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

MIT License

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

By use of a third party library GoMock which intergrates well with the testing library

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

Yes

The short answer is yes, by use of table tests which are a great way of performing multiple I/O tests on a function or behaviour with minimal code

Yes

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