Knapsack Pro

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

JBehave

https://jbehave.org/

Kiwi

https://github.com/kiwi-bdd/Kiwi
Programming language

Java

Swift

Category

Acceptance Testing

Unit Testing

General info

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

Kiwi is a Behavior Driven Development library for iOS development

The goal behind Kiwi is to provide a BDD library that is simple to setup and use, and create tests that are more readable than what is possible with the bundled test framework.
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

Yes

Kiwi 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 behaviour (scenarios) with JBehave

Yes

You can test front-end components with kiwi
Server-side
Allows testing the bahovior of a server-side code

JBehave tests scenarios and behaviours of components, it can test back-end behaviour

Yes

You can test back-end components with kiwi
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

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.

Yes

You can define group fixtures with JBehave

Yes

kiwi has a beforeEach(aBlock) which is run before every 'it' block in all enclosed contexts. Code that sets up the particular context should go here and afterEach(aBlock) which is run after every it block in all enclosed contexts
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.

No

Yes

through the beforeAll(aBlock) and afterAll(aBlock) functions.
Licence
Licence type governing the use and redistribution of the software

BSD-style license

Proprietary, Open source

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)

The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit

Yes

Kiwi has inbuilt support for stubs and mocks,including null mocks, class mocks, protocol mocks
Grouping
Allows organizing tests in groups

N/A

Yes

Kiwi uses the block syntax in iOS to define groups of assertions and share setup state between collections of tests
Other
Other useful information about the testing framework