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

	csUnit http://www.csunit.org/	JDave http://jdave.org/
Programming language	.NET	Java
Category	Unit Testing	Acceptance Testing
General info	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#	JDave is a BDD framework for Java JDave is inspired by RSpec and integrates JMock 2 as mocking framework and Hamcrest as matching library. It uses JUnit adapter to launch JDave specifications. This way it is possible to have IDE, build tool and coverage tool support from day one.
xUnit Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.	Yes csUnit is an xUnit type testing framework and follows xUnit concepts	No
Client-side Allows testing code execution on the client, such as a web browser	Yes You can unit test front-end components of your applications with csUnit	Yes Front-end behaviour can be tested with JDave
Server-side Allows testing the bahovior of a server-side code	Yes You can unit test back-end components of your applications with csUnit	Yes JDave can test server-side behaviour
Fixtures Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test	Yes csUnit has fixture methods such as setup and teardown methods	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 Group fixtures are available in csUnit	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.	N/A	N/A
Licence Licence type governing the use and redistribution of the software	zlib 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)	You can write your own mock objects manually	Yes It integrates JMock 2 as mocking framework
Grouping Allows organizing tests in groups	Yes It contains recipes for combining several test assemblies into one test suite	Yes Specifications can be grouped by tagging them with @Group annotation.
Other Other useful information about the testing framework