Test::Unit vs JDave comparison of testing frameworks
What are the differences between Test::Unit and JDave?

	Test::Unit https://test-unit.github.io/	JDave http://jdave.org/
Programming language	Ruby	Java
Category	Unit Testing, Intergration Testing	Acceptance Testing
General info	Test::Unit is a unit testing framework for Ruby Test::Unit is an implementation of the xUnit testing framework for ruby which is used for Unit Testing. However Test::Unit has been left in the standard library to support legacy test suites therefore if you are writing new test code use Minitest instead of Test::Unit	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 test-unit is a xUnit family unit testing framework for Ruby	No
Client-side Allows testing code execution on the client, such as a web browser	It could have tested some front-end components but its now legacy hence wouldn't work with the many new front-end components	Yes Front-end behaviour can be tested with JDave
Server-side Allows testing the bahovior of a server-side code	Yes	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 Fixture methods are available through its ClassMethods Module	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 fixture methods are supported	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	LGPLv2.1, Ruby Licence	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)	No	Yes It integrates JMock 2 as mocking framework
Grouping Allows organizing tests in groups	No	Yes Specifications can be grouped by tagging them with @Group annotation.
Other Other useful information about the testing framework