Knapsack Pro

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

StoryPlayer

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

JBehave

https://jbehave.org/
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

JBehave is a Behaviour-Driven Development testing framework for java

JBehave is a Behaviour Driven Development framework. It intends to provide an intuitive and accessible way for automated acceptance testing
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 front-end behaviour (scenarios) with JBehave
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

JBehave tests scenarios and behaviours of components, it can test back-end behaviour
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

You have a few options for using fixtures in JBehave: you can run your steps before/after each scenario by using LifeCycle: you can use @BeforeStory and @AfterStory annotations or you can define a dummy scenario with your setup/teardown steps
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 define group fixtures with JBehave
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.

No

Licence
Licence type governing the use and redistribution of the software

New BSD License

BSD-style 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

The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit
Grouping
Allows organizing tests in groups

Yes

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

N/A

Other
Other useful information about the testing framework