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

	Sleipnir https://github.com/railsware/Sleipnir	StoryPlayer http://datasift.github.io/storyplayer/
Programming language	Swift	PHP
Category	Unit Testing, Acceptance Testing	Unit testing, Functional Testing
General info	Sleipnir is a BDD-style framework for Swift Sleipnir is a pure Swift BDD testing framework inspired by cedar, that is not dependent on NSObject, and does not use XCTest. Sleipnir has nice command line output and support for custom test reporters and other features, like seeded random tests invocation, focused and excluded examples/groups	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.	N/A	No
Client-side Allows testing code execution on the client, such as a web browser	Yes You can test front-end behaviour by defining specifications for classes, objects and functions	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 You can test back-end behaviour by defining specifications for classes, objects and functions in the back-end	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 Fixtures are available by using beforeEach{ } and afterEach{ } to setup the test parameters	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 are available through the beforeAll{} and afterAll{} blocks to setup group fixtures	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	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 Yes, developers can create mock objects with sleipnir using a third party library like Cuckoo.	By using a library like mockery which intergrates well with storyplayer
Grouping Allows organizing tests in groups	Yes You can declare example groups with Slepnir	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework