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

	Cucumber https://github.com/cucumber/cucumber-ruby	StoryPlayer http://datasift.github.io/storyplayer/
Programming language	Ruby	PHP
Category	Acceptance Testing	Unit testing, Functional Testing
General info	An automation tool for Behavior-Driven Development The specifications are written in plain texts, which allows them to be easily understandable for all stakeholders. Cucumber Framework also supports languages beyond Ruby e.g. Java, JavaScript and Scala.	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	No
Client-side Allows testing code execution on the client, such as a web browser	Yes You can test the front-end part like the GUI using cucumber and selenium, they integrate well to test your front-end.	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 components such as APIs using rest & soap clients, and databases using whatever client libraries were provided by the libraries that existed in those stacks	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 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 Using the cucumber extension aruba you can create fixures in two steps: 1.Create a fixtures-directory; 2.Create fixture files in this directory	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 You can group your fixtures inside your fixtures directories	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 using all of RSpec’s supported mocking frameworks (RSpec, Mocha, RR, Flexmock)	By using a library like mockery which intergrates well with storyplayer
Grouping Allows organizing tests in groups	Yes Cucumber allows the use of tag Cucumber feature files or individual tests to group tests. Then, you can pass a Cucumber tagged expression at test execution that specifies the tag (grouped) tests to run. https://www.toolsqa.com/cucumber/cucumber-tags/	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework