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

Shoulda

https://github.com/thoughtbot/shoulda

JBehave

https://jbehave.org/
Programming language

Ruby

Java

Category

Acceptance Testing

General info

Meta gem containing Shoulda Context and Shoulda Matchers

Shoulda contains two other gems: Should Context and Shoulda Matchers. Should Context allows better naming and grouping of your tests. Shoulda Matchers provides a set of "matchers", i.e. methods that allow you to write much more concise assertions.

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

N/A

Yes

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

N/A

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

N/A

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)

N/A

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

Yes

N/A

Other
Other useful information about the testing framework

Shoulda Context is compatible with Minitest and Test::Unit. Shoulda Matchers is compatible with RSpec and Minitest.