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

Turnip

https://github.com/jnicklas/turnip

JBehave

https://jbehave.org/
Programming language

Ruby

Java

Category

Acceptance Testing, Integration Testing

Acceptance Testing

General info

Turnip is a Gherkin extension for RSpec

Turnip is an open source Ruby gem that provides a platform for acceptance tests.It combines Gherkin, a language defined by the Cucumber Behavior-Driven Development (BDD) tool to express requirements, and RSpec, an open source BDD tool for Ruby developers.

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.

No

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

Turnip can perform end-to-end tests therefore test front-end components and functionality

Yes

You can test front-end behaviour (scenarios) with JBehave
Server-side
Allows testing the bahovior of a server-side code

Yes

Turnip is used to test server-side behaviour and components

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

No

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.

No

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.

No

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

By intergrating with RSpec turnip has access to the rspec-mocks gem

The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit
Grouping
Allows organizing tests in groups

Yes

Turnip Integrates directly into your RSpec test suite which allows declaring example groups and contexts.

N/A

Other
Other useful information about the testing framework