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

	JBehave https://jbehave.org/	BeanTest https://github.com/NovatecConsulting/BeanTest
Programming language	Java	Java
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	A testing solution for Java EE applications BeanTest is a testing solution for Java EE Applications which combines the speed of unit tests with almost the coverage of integration tests with minimal configuration and with standard and well known frameworks like JPA, CDI, Mockito and Junit
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 You can test front-end components of your EE application
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 BeanTest is used to test business logic or the back-end that is information exchange between the database and the UI
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
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
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
Licence Licence type governing the use and redistribution of the software	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)	The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit	Yes You are able to provide your own Mocks in BeanTest to test external dependencies
Grouping Allows organizing tests in groups	N/A
Other Other useful information about the testing framework