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

	Quick https://github.com/quick/quick	StoryPlayer http://datasift.github.io/storyplayer/
Programming language	Swift	PHP
Category	Acceptance Testing, Unit Testing	Unit testing, Functional Testing
General info	Quick is a Swift (and Objective-C) testing framework. Quick is a behavior-driven development framework for Swift and Objective-C that is inspired by RSpec, Specta, and Ginkgo. Quick comes bundled with Nimble a matcher framework for your tests.	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.	Yes Yes, it is an xUnit style test framework	No
Client-side Allows testing code execution on the client, such as a web browser	Yes Developers can test front-end behaviour and components by defining front-end feature specifications	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 Developers can test back-end behaviour and components by defining back-end feature specifications	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 Quick contains fixture methods setup() and teardown() for setting up and destroying test environments	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 Yes, example groups (logical groupings of examples/tests) can share setup and teardown code	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.	N/A	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 Yes, developers can create mock objects with Quick using the Cuckoo library	By using a library like mockery which intergrates well with storyplayer
Grouping Allows organizing tests in groups	Yes In Quick test suites are named Specs, and every test suite you create starts off with a class inheriting from QuickSpec includes a main method, spec() which contains all the test cases.	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework