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

Lettuce

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

Cedar

https://github.com/cedarbdd/cedar
Programming language

Python

Swift

Category

Unit Testing, Acceptance Testing

Unit Testing

General info

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

Cedar is a BDD-style testing for swift using Objective-C

Cedar is a BDD-style Objective-C/Swift testing framework that has an expressive matcher DSL and convenient test doubles (mocks). It provides better organizational facilities than the tools provided by XCTest/OCUnit In environments where C++ is available, it provides powerful built-in matchers, test doubles and fakes
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

However It can generate xml results for behaviour tests xUnit style

Yes

Cedar is an xUnit style framework
Client-side
Allows testing code execution on the client, such as a web browser

Yes

By integrating Lettuce with Selenium’s Python bindings, you have a robust framework for testing Django applications. It can test front-end behaviour

Yes

You can test front-end components and behaviour with Cedar, its language is biased towards describing the behavior of your objects.
Server-side
Allows testing the bahovior of a server-side code

Yes

Lettuce can test various server and database behaviours and interactions

Yes

You can test back-end components with a bias towards their expected behaviour. Cedar specs also allow you to nest contexts so that it is easier to understand how your object behaves in different scenarios
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

N/A

Yes

Cedar has beforeEach and afterEach class methods which Cedar will look for on every class it loads. You can add these onto any class you compile into your specs and Cedar will run them
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

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

By using a third party library

N/A

Licence
Licence type governing the use and redistribution of the software

Unknown

MIT 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 adding the lettuce-tools library one has access to the Mock module to implement a configurable http REST mock.

Yes

Cedar contains inbuilt mock/test double functionality
Grouping
Allows organizing tests in groups

Yes

It allows grouping of tests

Yes

Cedar supports shared example groups. You can declare them in one of two ways: either inline with your spec declarations, or separately.
Other
Other useful information about the testing framework