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

JBehave

https://jbehave.org/

Ginkgo

http://onsi.github.io/ginkgo/
Programming language

Java

Go

Category

Acceptance Testing

Unit Testing, Intergration 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

BDD testing framework for Go

Ginkgo is a BDD testing framework for Go that has a great matcher library to go with it called Gomega and intergrates with the standard testing library
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

Yes, by creating unit tests then testing individual front-end components
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

Yes by creating unit tests then testing various back-end 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

N/A

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

N/A

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

They are available by running the command: 'ginko bootstrap'
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

Dvelopers can generate mocks by using the third party package 'gomock'
Grouping
Allows organizing tests in groups

N/A

Yes

Ginkgo allows you to group tests in 'Describe' and 'Context' container blocks. It also provides 'It' and 'Specify' blocks to hold your assertions
Other
Other useful information about the testing framework