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

	Cedar https://github.com/cedarbdd/cedar	unittest2 https://pypi.org/project/unittest2/
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	Unittest2 is a newer version on the inbuilt unit testing framework unittest To use o use unittest2 instead of unittest, simply replace 'import unittest' with 'import unittest2'. It has many new features such as: - addCleanups for better resource management; -many new assert methods; - assertRaises as context manager, with access to the exception afterwards; - test discovery and new command line options (including failfast and better handling of ctrl-C during test runs); - class and module level fixtures: setUpClass, tearDownClass, setUpModule, tearDownModule; -test skipping and expected failures and many more improvements on the API and bug fixes
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 unittest2 is a newer version of unittest which is an xUnit style framework for Python.
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 unittest2. function by function
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 We can write tests with unittest2 to test each function for server-side behaviour
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 unittest2 allows you to group your initialization code buy use of the 'setUp()' function and clean up code with 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 unittest2 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