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

	JBehave https://jbehave.org/	Turnip https://github.com/jnicklas/turnip
Programming language	Java	Ruby
Category	Acceptance Testing	Acceptance Testing, Integration 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	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.
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 You can test front-end behaviour (scenarios) with JBehave	Yes Turnip can perform end-to-end tests therefore test front-end components and functionality
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 Turnip is used to test server-side behaviour and components
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	No
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	No
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	BSD-style license	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)	The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit	Yes By intergrating with RSpec turnip has access to the rspec-mocks gem
Grouping Allows organizing tests in groups	N/A	Yes Turnip Integrates directly into your RSpec test suite which allows declaring example groups and contexts.
Other Other useful information about the testing framework