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

	Cedar https://github.com/cedarbdd/cedar	unittest https://docs.Python.org/3/library/unittest.html
Programming language	Swift	Python
Category	Unit Testing	Unit 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	unittest is a unit testing framework for Python The unittest test framework is Python’s xUnit style framework. It is a standard module that is bundled with Python and supports the automation and aggregation of tests and common setup and shutdown code for them.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	Yes Cedar is an xUnit style framework	Yes unittest is a xUnit style frameworkfor Python, it was previously called PyUnit.
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 Front-end functionality and behaviour can be tested by unittest.
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 Since the webserver funtionalities have their own features and each feature has its own functions, we can write tests with unittest to test each function
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 By use of the 'setUp()' function which is called to prepare the test fixture
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 unittest allows you to group your initialization code into a setUp function and clean up code in a tearDown function
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 unittest contains generator methods in the module 'unittest.TestCase'
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 Mocks are available from the library unittest.mock which allows you to replace parts of your system under test with mock objects
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 One can build suites either manually or use test discovery to build the suite automatically by scanning a directory
Other Other useful information about the testing framework