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

StoryPlayer

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

SpecFlow

https://specflow.org/
Programming language

PHP

.NET

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

SpecFlow is a test automation solution for .NET

SpecFlow is a test automation solution for .NET which follows the BDD paradigm, and is part of the Cucumber family. SpecFlow tests are written with Gherkin, using the official Gherkin parser which allows you to write test cases using natural languages and supports over 70 languages.
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

Front-end behaviour is tested. With specflow specifications of the expected behaviours are made and specflow tests against this
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

Back-end behaviour is tested. Specifications of the expected behaviours are made and specflow tests against them
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

BeforeTestRun and AfterTestRun are executed once for each thread which is a limitation of the current architecture.
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

N/A

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.

Yes

SpecFlow contains a generator component. The SpecFlow IDE integration tries to locate the generator component in your project structure, in order to use the generator version matching the SpecFlow runtime in your project
Licence
Licence type governing the use and redistribution of the software

New BSD License

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

Yes

Specflow intergrates well with mock to give it excellent mocking capabilities
Grouping
Allows organizing tests in groups

Yes

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

Yes

You can create test suites with specflow
Other
Other useful information about the testing framework