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

JBehave

https://jbehave.org/

Laravel Dusk

https://laravel.com/docs/5.8/dusk
Programming language

Java

PHP

Category

Acceptance Testing

Browser Automation

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

Laravel Dusk is an easy-to-use browser automation and testing API.

One can use Dusk to programmatically test applications, visit any website using a real Chrome browser, automate repetitive tasks, scrape information from other sites or test to make sure your app always works in the browser.
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

N/A

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

It is a browser automation tool which tests front-end components and functionality
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

Laravel provides a variety of tools to make it easier to test your database driven applications
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

N/A

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

Laravel provides helpers for mocking events, jobs, and facades out of the box or use Mockery or PHPUnit to create your own mocks or spies
Grouping
Allows organizing tests in groups

N/A

Yes

Using the 'dusk' which command accepts any argument that is normally accepted by the PHPUnit test runner, allowing you to run the tests for a given group.
Other
Other useful information about the testing framework