Knapsack Pro

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

StoryPlayer

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

Lettuce

https://pypi.org/project/lettuce/
Programming language

PHP

Python

Category

Unit testing, Functional Testing

Unit 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

Lettuce is a BDD testing tool for Python

Lettuce is a testing tool for Python which is inspired by Ruby's Cucumber that supports Gherkin. It can execute plain-text functional descriptions as automated tests for Python projects just like Cucumber does for Ruby
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

However It can generate xml results for behaviour tests xUnit style
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

By integrating Lettuce with Selenium’s Python bindings, you have a robust framework for testing Django applications. It can test front-end behaviour
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

Lettuce can test various server and database behaviours and interactions
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

N/A

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

By using a third party library
Licence
Licence type governing the use and redistribution of the software

New BSD License

Unknown

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

By adding the lettuce-tools library one has access to the Mock module to implement a configurable http REST mock.
Grouping
Allows organizing tests in groups

Yes

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

Yes

It allows grouping of tests
Other
Other useful information about the testing framework