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

Quick

https://github.com/quick/quick

Cedar

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

Swift

Swift

Category

Acceptance Testing, Unit Testing

Unit Testing

General info

Quick is a Swift (and Objective-C) testing framework.

Quick is a behavior-driven development framework for Swift and Objective-C that is inspired by RSpec, Specta, and Ginkgo. Quick comes bundled with Nimble a matcher framework for your tests.

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.

Yes

Yes, it is an xUnit style test framework

Yes

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

Yes

Developers can test front-end behaviour and components by defining front-end feature specifications

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

Developers can test back-end behaviour and components by defining back-end feature specifications

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

Quick contains fixture methods setup() and teardown() for setting up and destroying test environments

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

Yes, example groups (logical groupings of examples/tests) can share setup and teardown code

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.

N/A

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

Yes, developers can create mock objects with Quick using the Cuckoo library

Yes

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

Yes

In Quick test suites are named Specs, and every test suite you create starts off with a class inheriting from QuickSpec includes a main method, spec() which contains all the test cases.

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