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

	JBehave https://jbehave.org/	Atata https://atata.io/
Programming language	Java	.NET
Category	Acceptance 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	Atata is a C# / .NET test automation framework for web Atata is an open source test framework that uses fluent object pattern. It consists of the following concepts: components (controls and page objects), attributes of the control search, settings attributes, triggers, verification attributes and methods
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes You can use Atata with xUnit frameworks
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 Atata is based on selenium and is used for browser automation. You can test various front-end functionalities and behaviours
Server-side Allows testing the bahovior of a server-side code	JBehave tests scenarios and behaviours of components, it can test back-end behaviour	No
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	Apache License 2.0
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
Grouping Allows organizing tests in groups	N/A
Other Other useful information about the testing framework