Knapsack Pro

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

Cedar

https://github.com/cedarbdd/cedar

Sleipnir

https://github.com/railsware/Sleipnir
Programming language

Swift

Swift

Category

Unit Testing

Unit Testing, Acceptance Testing

General info

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

Sleipnir is a BDD-style framework for Swift

Sleipnir is a pure Swift BDD testing framework inspired by cedar, that is not dependent on NSObject, and does not use XCTest. Sleipnir has nice command line output and support for custom test reporters and other features, like seeded random tests invocation, focused and excluded examples/groups
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

Yes

Cedar is an xUnit style framework

N/A

Client-side
Allows testing code execution on the client, such as a web browser

Yes

You can test front-end components and behaviour with Cedar, its language is biased towards describing the behavior of your objects.

Yes

You can test front-end behaviour by defining specifications for classes, objects and functions
Server-side
Allows testing the bahovior of a server-side code

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

Yes

You can test back-end behaviour by defining specifications for classes, objects and functions in the back-end
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

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

Yes

Fixtures are available by using beforeEach{ } and afterEach{ } to setup the test parameters
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

Yes

Group fixtures are available through the beforeAll{} and afterAll{} blocks to setup 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.

N/A

N/A

Licence
Licence type governing the use and redistribution of the software

MIT License

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

Cedar contains inbuilt mock/test double functionality

Yes

Yes, developers can create mock objects with sleipnir using a third party library like Cuckoo.
Grouping
Allows organizing tests in groups

Yes

Cedar supports shared example groups. You can declare them in one of two ways: either inline with your spec declarations, or separately.

Yes

You can declare example groups with Slepnir
Other
Other useful information about the testing framework