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

StoryPlayer

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

JUnit

https://junit.org/junit5/
Programming language

PHP

Java

Category

Unit testing, Functional Testing

Unit Testing, Regression 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

JUnit is an open source Unit testing framework for java

JUnit is useful for developers to write and run repeatable tests. JUnit has been crucial in the development of test driven development and is partof the xUnit family of unit testing frameworks
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

Yes

It is an instance of the xUnit architecture for unit testing frameworks.
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 such as individual classes and functions that create the 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 classes and functions that compose the back-end such as database connections and so on
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

JUnit contains a setUp() method, which runs before every test invocation and a tearDown() method, which runs after every test method.
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 use setUp() and tearDown() inbuilt functions as 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

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.

You can use JUnit-quickcheck to generate test data
Licence
Licence type governing the use and redistribution of the software

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)

By using a library like mockery which intergrates well with storyplayer

JUnit does not support mocking internally but you can use a mock framework like Mockito to generate mock objects.
Grouping
Allows organizing tests in groups

Yes

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

Yes

In JUnit you can create a test suite that bundles a few unit test cases and runs them together. You use both @RunWith and @Suite annotation are used to run the suite test.
Other
Other useful information about the testing framework