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

	JUnit https://junit.org/junit5/	Cedar https://github.com/cedarbdd/cedar
Programming language	Java	Swift
Category	Unit Testing, Regression Testing	Unit Testing
General info	JUnit is an open source Unit testing framework for java JUnit is useful for developers to write and run repeatable tests. JUnit has been crucial in the development of test driven development and is partof the xUnit family of unit testing frameworks	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.	Yes It is an instance of the xUnit architecture for unit testing frameworks.	Yes Cedar is an xUnit style framework
Client-side Allows testing code execution on the client, such as a web browser	Yes You can test front-end components such as individual classes and functions that create the front-end	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 You can test classes and functions that compose the back-end such as database connections and so on	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 JUnit contains a setUp() method, which runs before every test invocation and a tearDown() method, which runs after every test method.	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 You can use setUp() and tearDown() inbuilt functions as 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.	You can use JUnit-quickcheck to generate test data	N/A
Licence Licence type governing the use and redistribution of the software		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)	JUnit does not support mocking internally but you can use a mock framework like Mockito to generate mock objects.	Yes Cedar contains inbuilt mock/test double functionality
Grouping Allows organizing tests in groups	Yes In JUnit you can create a test suite that bundles a few unit test cases and runs them together. You use both @RunWith and @Suite annotation are used to run the suite test.	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