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

Tape

https://github.com/substack/tape

Cedar

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

JavaScript

Swift

Category

Unit Testing, Intergration Testing

Unit Testing

General info

tap-producing test harness for node and browsers.

Tape API is a small superset of the node core assert module

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

It does support xUnit output

Yes

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

Yes

You can write tests for any part of your front-end code to test any component or functionality

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

With tape you can test any back-end component, behaviour and functionality after all it supports TAP (Test Anything Protocol)

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

No

Tape contains only the essential features for making assertions on your code but there is a package called redtape that extends tape to give you beforeEach and afterEach functionality

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.

No

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.

No

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)

No

Tape is a minimalistic framework that provides only essential features to make your assertions about your code

Yes

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

No

Tape contains only the essential features for making assertions on your code

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