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

	Cedar https://github.com/cedarbdd/cedar	Cucumber https://github.com/cucumber/cucumber-ruby
Programming language	Swift	Ruby
Category	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	An automation tool for Behavior-Driven Development The specifications are written in plain texts, which allows them to be easily understandable for all stakeholders. Cucumber Framework also supports languages beyond Ruby e.g. Java, JavaScript and Scala.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	Yes Cedar is an xUnit style framework	No
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 the front-end part like the GUI using cucumber and selenium, they integrate well to test your front-end.
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 components such as APIs using rest & soap clients, and databases using whatever client libraries were provided by the libraries that existed in those stacks
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
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 Using the cucumber extension aruba you can create fixures in two steps: 1.Create a fixtures-directory; 2.Create fixture files in this directory
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	Yes You can group your fixtures inside your fixtures directories
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 By using all of RSpec’s supported mocking frameworks (RSpec, Mocha, RR, Flexmock)
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 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/
Other Other useful information about the testing framework