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

	Cedar https://github.com/cedarbdd/cedar	Behat https://docs.behat.org/en/latest/
Programming language	Swift	PHP
Category	Unit Testing	Functional/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	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
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 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.
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 Behat can be used for Data Integrity Testing to verify that database operations are functioning properly
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	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.
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 Behat allows for group fixtures
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	By use of third party libraries like moodle-behat-generators
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	By using third party libraries like Mock and Prophecy
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 You can use tags to group features and scenarios together, independent of your file and directory structure
Other Other useful information about the testing framework