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

StoryPlayer

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

Kiwi

https://github.com/kiwi-bdd/Kiwi
Programming language

PHP

Swift

Category

Unit testing, Functional 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

Kiwi is a Behavior Driven Development library for iOS development

The goal behind Kiwi is to provide a BDD library that is simple to setup and use, and create tests that are more readable than what is possible with the bundled test framework.
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

Yes

Kiwi is an xUnit style framework
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

You can test front-end components with kiwi
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

You can test back-end components with kiwi
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

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

kiwi has a beforeEach(aBlock) which is run before every 'it' block in all enclosed contexts. Code that sets up the particular context should go here and afterEach(aBlock) which is run after every it block in all enclosed contexts
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

through the beforeAll(aBlock) and afterAll(aBlock) functions.
Licence
Licence type governing the use and redistribution of the software

New BSD License

Proprietary, Open source

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

Kiwi has inbuilt support for stubs and mocks,including null mocks, class mocks, protocol mocks
Grouping
Allows organizing tests in groups

Yes

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

Yes

Kiwi uses the block syntax in iOS to define groups of assertions and share setup state between collections of tests
Other
Other useful information about the testing framework