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

	JBehave https://jbehave.org/	csUnit http://www.csunit.org/
Programming language	Java	.NET
Category	Acceptance 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	csUnit is an open source unit testing tool for the .NET Framework csUnit is designed to work with any .NET compliant language. It has specifically been tested with C#, Visual Basic .NET, Managed C++, and J#
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	No	Yes csUnit is an xUnit type testing framework and follows xUnit concepts
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 You can unit test front-end components of your applications with csUnit
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 back-end components of your applications with csUnit
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	Yes csUnit has fixture methods such as setup and teardown methods
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	Yes Group fixtures are available in csUnit
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	zlib 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 write your own mock objects manually
Grouping Allows organizing tests in groups	N/A	Yes It contains recipes for combining several test assemblies into one test suite
Other Other useful information about the testing framework