Test::Unit vs Cedar comparison of testing frameworks
What are the differences between Test::Unit and Cedar?

Test::Unit

https://test-unit.github.io/

Cedar

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

Ruby

Swift

Category

Unit Testing, Intergration Testing

Unit Testing

General info

Test::Unit is a unit testing framework for Ruby

Test::Unit is an implementation of the xUnit testing framework for ruby which is used for Unit Testing. However Test::Unit has been left in the standard library to support legacy test suites therefore if you are writing new test code use Minitest instead of Test::Unit

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

test-unit is a xUnit family unit testing framework for Ruby

Yes

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

It could have tested some front-end components but its now legacy hence wouldn't work with the many new front-end components

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

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 available through its ClassMethods Module

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 fixture methods 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.

No

N/A

Licence
Licence type governing the use and redistribution of the software

LGPLv2.1, Ruby Licence

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

Yes

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

No

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