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

	StoryPlayer http://datasift.github.io/storyplayer/	Robot Framework https://robotframework.org/
Programming language	PHP	Python
Category	Unit testing, Functional Testing	Acceptance 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	Robot is a Python framework used for acceptance/functional testing Robot is an automated test framework which has a simple plain text syntax and can be extended easily with Python or Java libraries. It can run on the .net-based IronPython and on Jython which is Java based.
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 Robot has a rich library and can also be easily integrated with Selenium for browser automation to test front-end components
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 Robot can be used for back-end tests as well
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	There is no inbuilt way to work with fixtures in Robot however it can integrate with unittest and use fixtures that way
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	By integrating with unittest
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 Robot has a library called the Robot Framework Faker library. It contains 147 keywords used for generating random test data
Licence Licence type governing the use and redistribution of the software	New BSD License	Apache License 2.0
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 Robot can access Python's mock library for mocking
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	Yes One can create a test suite with Robot
Other Other useful information about the testing framework