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

	Concordion https://concordion.org/	StoryPlayer http://datasift.github.io/storyplayer/
Programming language	Java	PHP
Category		Unit testing, Functional Testing
General info	Concordion is a tool used to write and manage automated acceptance tests in Java based projects Concordion specifications are written in Markdown, HTML or Excel and then instrumented with special links, attributes or comments respectively. When the corresponding test fixture class is run, Concordion interprets the instrumentation to execute the test. Concordion lets you write them in normal language using paragraphs, tables and proper punctuation. This makes specification more natural to read and write, and helps everyone to understand and agree about what a feature is supposed to do.	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 specify tests for front-end components and functionality with concordion	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 server-side components and functionality with concordion.	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 Concordion contains fixtures which correspond to a specific instrumentation within the code. That is when specifications are written they are instrumented with special links, attributes or comments which are then run with their corresponding fixtures	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 One can group fixtures in concordion	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	Apache License 2.0	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 use of third party libraries like mockito	By using a library like mockery which intergrates well with storyplayer
Grouping Allows organizing tests in groups	Yes One can group tests into suites	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework