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

	JBehave https://jbehave.org/	Spinach https://github.com/codegram/spinach
Programming language	Java	Ruby
Category	Acceptance Testing	Acceptance 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	Spinach is a BDD framework on top of Gherkin Spinach is a high-level BDD framework that leverages the Gherkin language to help define executable specifications of your application or library's acceptance criteria.
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	N/A
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 any server-side behaviour with Spinach
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	Yes Spinach has inbuilt generator methods
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 Spinach can access the rspec-mocks methods
Grouping Allows organizing tests in groups	N/A	Yes Spinach Integrates with your RSpec test suite which allows declaring example groups and contexts.
Other Other useful information about the testing framework