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

StoryPlayer

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

DOH

https://dojotoolkit.org/reference-guide/1.10/util/doh.html
Programming language

PHP

JavaScript

Category

Unit testing, Functional Testing

Unit 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

D.O.H means Dojo Objective Harness, it's a test framework for the DOJO web apps which tests and runs on the browser and on cloud test execution services like Browserstack

Dojo is a Typescript framework build for modern web application, and D.O.H is a basically unit test library to test JavaScript functions and custom widgets
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

DOH is both flexible and extendable and runs in many environments including many browsers to test various front-end functionalities and components
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

Pieces of back-end code can be tested with DOH as it performs Unit tests. It is flexible enough to test server-side behaviour and functionality
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

It has various fixture methods like setUp(), tearDown() and Performance test fixtures which are just like a regular test fixtures, but with extra options. Specifically, it uses 'testType' to mark it as a "perf" test, which instructs the D.O.H. runner to treat the tests as performance and use the calibrate and execute test runner
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

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

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

FreeBSD 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

N/A

Grouping
Allows organizing tests in groups

Yes

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

Yes

There is a function that allows you to group tests, the 'doh.register(...)' function. It's most commonly used for registering Unit Tests
Other
Other useful information about the testing framework