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

	Behat https://docs.behat.org/en/latest/	JBehave https://jbehave.org/
Programming language	PHP	Java
Category	Functional/Acceptance Testing	Acceptance Testing
General info	Behat is an open source Behavior-Driven Development framework for PHP. Behat uses the StoryBDD subtype of behaviour-driven development (the other subtype is SpecBDD); This means the tests we write with Behat look rather like stories than code. It is inspired by Ruby's Cucumber	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 To enable Behat to test a website, you need to add Mink and a browser emulator (selenium maybe, though slow) to the mix. Mink methods are the connector between Behat and an extensive list of available drivers, and they provide a consistent testing API.	Yes You can test front-end behaviour (scenarios) with JBehave
Server-side Allows testing the bahovior of a server-side code	Yes Behat can be used for Data Integrity Testing to verify that database operations are functioning properly	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	Yes One can use the 'Doctrinefixturesbundle' to create the required fixture loaders and load them in our Behat scenarios when required, using the 'BeforeScenario' hook.	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.	Yes Behat allows for group fixtures	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.	By use of third party libraries like moodle-behat-generators	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)	By using third party libraries like Mock and Prophecy	The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit
Grouping Allows organizing tests in groups	Yes You can use tags to group features and scenarios together, independent of your file and directory structure	N/A
Other Other useful information about the testing framework