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

	Cedar https://github.com/cedarbdd/cedar	Jnario http://jnario.org/
Programming language	Swift	Java
Category	Unit Testing	Acceptance 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	Jnario is a test framework for Java focusing on the design and documentation aspects of testing Jnario is based on Xtend and consists of two domain-specific languages, one for writing readable acceptance tests, the other for succinct unit tests. Together they are well suited for behavior-driven development of Java programs.
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 It is an xUnit type testing framework
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 You can write scenarios to test various front-end behaviours using 'Given', 'When', 'Then' steps to describe simple scenarios
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 You can write unit tests to test server side behaviours and components using Jnario specs
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 It contains the Setup & Teardown functions similar to JUnit but less verbose
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 The Setup & Teardown functions can be used as 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	N/A
Licence Licence type governing the use and redistribution of the software	MIT License	Eclipse Public License v1.0
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 You can implement mocking through the use of a third partylibrary like Mockito
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 Jnario Suites allows you to group multiple specifications into suites and execute them together, you do this using the suite wizard
Other Other useful information about the testing framework