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

	StoryPlayer http://datasift.github.io/storyplayer/	Cucumber-JVM https://github.com/cucumber/cucumber-jvm
Programming language	PHP	Java
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	Cucumber-JVM is a pure Java implementation of Cucumber The specifications are written in plain texts, which allows them to be easily understandable by all stakeholders.
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 You can test the front-end part like the GUI using cucumber with serenity, they integrate well to test your front-end.
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 such as API's using rest&soap clients, and databases
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	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
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 You can group your fixtures inside your fixtures directories
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.	N/A
Licence Licence type governing the use and redistribution of the software	New BSD License	MIT 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)	By using a library like mockery which intergrates well with storyplayer	Yes By using all of RSpec’s supported mocking frameworks (RSpec, Mocha, RR, Flexmock)
Grouping Allows organizing tests in groups	Yes Storyplayer’s job is to execute a suite of functional tests	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/
Other Other useful information about the testing framework