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

	Selenium https://pypi.org/project/selenium/	StoryPlayer http://datasift.github.io/storyplayer/
Programming language	Python	PHP
Category	Web Automation	Unit testing, Functional Testing
General info	Selenium is an open source tool used to test web applications Selenium is a powerful testing tool which can send standard Python commands to different browsers, despite variations in browser design. It also provides extensions to emulate user interaction with browsers, a distribution server for scaling browser allocation, and the infrastructure for implementations of the W3C WebDriver specification that lets you write interchangeable code for all major web browsers	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 It is primarily a browser automation tool which tests front-end 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 It can perform Unit tests and can test various components and behaviours in the backend using a BDD or TDD approach	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 writing your Selenium WebDriver tests in PyTest, this gives you access to Pytest's powerful fixture model	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.	Yes One can group fixtures if accessing Pytest's fixture model	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 By using a library such as Faker or Fake-factory	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	Apache License 2.0	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)	Yes It includes support for mocking	By using a library like mockery which intergrates well with storyplayer
Grouping Allows organizing tests in groups	Yes By using the TestNG feature with which we can create groups and maintain them easily	Yes Storyplayer’s job is to execute a suite of functional tests
Other Other useful information about the testing framework