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

	Codedeception https://codeception.com/	Cedar https://github.com/cedarbdd/cedar
Programming language	PHP	Swift
Category	Unit Testing, Acceptance Testing/Functional Testing	Unit Testing
General info	Codeception is a full-stack testing framework for PHP It is inspired by BDD and provides a way of writing acceptance, functional and even unit tests. It is powered by PHPUnit.	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 One is able to write acceptance tests which are used to look at functionality from a user's perspective. It is able to look at pages in browser (Chrome, Firefox or PhpBrowser)	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 It supports back-end tests, by writing functionaltests one can be able to test server behaviour	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 define a fixture and write the test with Codedeception, use the yii2-codedeceptionextention which will autoload fixtures for you	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 One can define 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.	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 Codeception provides Codeception\Stub library for building mocks and stubs for tests	Yes Cedar contains inbuilt mock/test double functionality
Grouping Allows organizing tests in groups	Yes Codeception consists of three so-called “suites”: A “unit suite” for all unit tests, a “functional suite” for all functional tests, and an “acceptance suite” for all acceptance tests.	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