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

	Concordion https://concordion.org/	JBehave https://jbehave.org/
Programming language	Java	Java
Category		Acceptance Testing
General info	Concordion is a tool used to write and manage automated acceptance tests in Java based projects Concordion specifications are written in Markdown, HTML or Excel and then instrumented with special links, attributes or comments respectively. When the corresponding test fixture class is run, Concordion interprets the instrumentation to execute the test. Concordion lets you write them in normal language using paragraphs, tables and proper punctuation. This makes specification more natural to read and write, and helps everyone to understand and agree about what a feature is supposed to do.	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 You can specify tests for front-end components and functionality with concordion	Yes You can test front-end behaviour (scenarios) with JBehave
Server-side Allows testing the bahovior of a server-side code	Yes You can test server-side components and functionality with concordion.	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 Concordion contains fixtures which correspond to a specific instrumentation within the code. That is when specifications are written they are instrumented with special links, attributes or comments which are then run with their corresponding 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 One can group fixtures in concordion	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	Apache License 2.0	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)	Yes By use of third party libraries like mockito	The best way to mock is to use third party libraries like Mockito, Jmock or Jmockit
Grouping Allows organizing tests in groups	Yes One can group tests into suites	N/A
Other Other useful information about the testing framework