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

	Peridot http://peridot-php.github.io/	JBehave https://jbehave.org/
Programming language	PHP	Java
Category	Unit Testing	Acceptance Testing
General info	Peridot is a lightweight, extensible testing framework for PHP It features an event-driven architecture that allows testers to easily customize the framework via plugins and reporters, and uses the 'describe-it', syntax making the testing language clear and readable	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 Front-end components can be tested with Peridot	Yes You can test front-end behaviour (scenarios) with JBehave
Server-side Allows testing the bahovior of a server-side code	Yes Back-end componets and behaviours can be tested as small units	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 Peridot has several methods that allow one to create and define fixtures	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 There are methods to create group fixtures in Peridot	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)	Peridot does not include mocking out of the box but there are some great tools like 'Mockery' and 'Prophecy' which Peridot intergrates very well with	The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit
Grouping Allows organizing tests in groups	Yes By use of describe and context blocks and it has a Runner which is responsible for running a given Suite.	N/A
Other Other useful information about the testing framework