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

Cedar

https://github.com/cedarbdd/cedar

JBehave

https://jbehave.org/
Programming language

Swift

Java

Category

Unit Testing

Acceptance 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

JBehave is a Behaviour-Driven Development testing framework for java

JBehave is a Behaviour Driven Development framework. It intends to provide an intuitive and accessible way for automated acceptance testing
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

Yes

Cedar is an xUnit style framework

No

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 test front-end behaviour (scenarios) with JBehave
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

JBehave tests scenarios and behaviours of components, it can test back-end 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

You have a few options for using fixtures in JBehave: you can run your steps before/after each scenario by using LifeCycle: you can use @BeforeStory and @AfterStory annotations or you can define a dummy scenario with your setup/teardown steps
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

You can define group fixtures with JBehave
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

No

Licence
Licence type governing the use and redistribution of the software

MIT License

BSD-style 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

The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit
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.

N/A

Other
Other useful information about the testing framework