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

Testify

https://github.com/Yelp/Testify

Cedar

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

Python

Swift

Category

Unit Testing

Unit Testing

General info

A Python unit testing framework modelled after unittest

Testify is modelled after unittest but has more features while still supporting unittest classes. It has more pythonic naming conventions, an better test runner output visually, a decorator-based approach to fixture methods among many other features

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

Yes

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

Yes

Front-end functionality and behaviour can be tested by Testify.

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

Testify can test various server and database behaviours and functionality

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

Yes

Fixture methods are supported and it follows a decorator based approach, that is they are written similar to decorators

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.

Yes

Group fixtures are supported

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

One can create generator methods to yield runnable test methods which will pick out the test methods from your TestCases, and then exclude any in any of your exclude_suites method.If there are any require_suites, it will then further limit itself to test methods in those suites.

N/A

Licence
Licence type governing the use and redistribution of the software

Apache License 2.0

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)

Yes

It includes the turtle mock object library

Yes

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

Yes

Testify includes support for detecting and running test suites, grouped by modules, classes, or individual test methods.

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