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

	JBehave https://jbehave.org/	Artos https://www.theartos.com/
Programming language	Java	Java
Category	Acceptance Testing	Functional Testing, End-to-End Testing, Unit 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	Artos is an opensource BDD testing framework for writing Unit, Intergration and Functional tests Artos includes pre-configured logging framework and extent reports, utilities to write flow for manual/semi-automated testing and supports BDD testing using cucumber scripts.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes It is a xUnit style framework
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 With Artos you can perform unit tests on 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 You can unit test server side behaviours and functionalities by testing specific back-end classes and functions
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	You can use a third party library like mockito
Grouping Allows organizing tests in groups	N/A	Yes Artos allows creation of test suites and they are run by use of a test script
Other Other useful information about the testing framework