Cucumber-JVM vs Cedar comparison of testing frameworks
What are the differences between Cucumber-JVM and Cedar?

Cucumber-JVM

https://github.com/cucumber/cucumber-jvm

Cedar

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

Java

Swift

Category

Acceptance Testing

Unit Testing

General info

Cucumber-JVM is a pure Java implementation of Cucumber

The specifications are written in plain texts, which allows them to be easily understandable by all stakeholders.

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

You can test the front-end part like the GUI using cucumber with serenity, they integrate well to test your front-end.

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

You can test back-end components such as API's using rest&soap clients, and databases

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

Using the cucumber extension aruba you can create fixures in two steps: 1.Create a fixtures-directory; 2.Create fixture files in this directory

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

You can group your fixtures inside your fixtures directories

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

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

By using all of RSpec’s supported mocking frameworks (RSpec, Mocha, RR, Flexmock)

Yes

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

Yes

Cucumber allows the use of tag Cucumber feature files or individual tests to group tests. Then, you can pass a Cucumber tagged expression at test execution that specifies the tag (grouped) tests to run. https://www.toolsqa.com/cucumber/cucumber-tags/

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