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

StoryPlayer

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

TestNG

https://testng.org/doc/documentation-main.html
Programming language

PHP

Java

Category

Unit testing, Functional Testing

Unit Testing, Intergration Testing, End-to-End 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

TestNG is a testing framework for the Java programming language inspired by JUnit and NUnit

TestNG is similar to JUnit and NUnit but with newer functionalities such as: annotations, test that your code is multithread safe, flexible test configuration, support for data-driven testing (with @DataProvider), support for parameters, powerful execution model (no more TestSuite) and more... It's also designed to cover all categories of tests unit, functional, end-to-end, intergration... etc
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

The scope of testing with testNg is wide and you can test various front-end functionalities and behaviours with it
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 server-side functionalities and behaviours with TestNg
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

Fixtures are inbuilt into testNG, these are the annotations which are: @BeforeSuite, @AfterSuite, @BeforeTest, @AfterTest, @BeforeGroups, @AfterGroups, @BeforeClass, @AfterClass, @BeforeMethod, @AfterMethod
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 various fixtures to setup environments for group tests
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

Apache License 2.0

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

Yes

By Use of an external library like mockit which intergrates well with testNG
Grouping
Allows organizing tests in groups

Yes

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

Yes

Multiple test cases can be grouped more easily by converting them into testng.xml file, in which you can make priorities which test case should be executed first
Other
Other useful information about the testing framework