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

Jasmine

https://github.com/jasmine/jasmine

StoryPlayer

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

JavaScript

PHP

Category

Unit Testing, End-to-End Testing

Unit testing, Functional Testing

General info

JS Unit test framework, BDD based for Node.JS applications used with Angular.JS web applications and also paired with 'Karma' task runner

It's a BDD (Behavior Driven Development) test framework for JavaScript especially designed for manual QAs to understand the automation tests. It does not depend on the any JavaScript framework or browser. So it's very well suited for Node.js projects and websites

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

Jasmine works well in and with browsers to test client-side components and functionality

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

Jasmine works with NodeJs to test its back-end components and behaviour

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

By using 'jasmine-fixture' which can help write specs that interact with the DOM making it easier to injectHTML 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.

N/A

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

MIT License

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 a plugin called jasmine-ajax that allows ajax calls to be mocked out in tests

By using a library like mockery which intergrates well with storyplayer
Grouping
Allows organizing tests in groups

Yes

Using the describe function which is for grouping related tests, typically each test file has one at the top level.

Yes

Storyplayer’s job is to execute a suite of functional tests
Other
Other useful information about the testing framework