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

Behat

https://docs.behat.org/en/latest/

Cedar

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

PHP

Swift

Category

Functional/Acceptance Testing

Unit Testing

General info

Behat is an open source Behavior-Driven Development framework for PHP.

Behat uses the StoryBDD subtype of behaviour-driven development (the other subtype is SpecBDD); This means the tests we write with Behat look rather like stories than code. It is inspired by Ruby's Cucumber

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

To enable Behat to test a website, you need to add Mink and a browser emulator (selenium maybe, though slow) to the mix. Mink methods are the connector between Behat and an extensive list of available drivers, and they provide a consistent testing API.

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

Behat can be used for Data Integrity Testing to verify that database operations are functioning properly

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

One can use the 'Doctrinefixturesbundle' to create the required fixture loaders and load them in our Behat scenarios when required, using the 'BeforeScenario' hook.

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

Behat allows for group fixtures

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.

By use of third party libraries like moodle-behat-generators

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)

By using third party libraries like Mock and Prophecy

Yes

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

Yes

You can use tags to group features and scenarios together, independent of your file and directory structure

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