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

	Test::Unit https://test-unit.github.io/	BeanTest https://github.com/NovatecConsulting/BeanTest
Programming language	Ruby	Java
Category	Unit Testing, Intergration Testing	Unit Testing, Intergration 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	A testing solution for Java EE applications BeanTest is a testing solution for Java EE Applications which combines the speed of unit tests with almost the coverage of integration tests with minimal configuration and with standard and well known frameworks like JPA, CDI, Mockito and Junit
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 You can test front-end components of your EE application
Server-side Allows testing the bahovior of a server-side code	Yes	Yes BeanTest is used to test business logic or the back-end that is information exchange between the database and the UI
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
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
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	LGPLv2.1, Ruby Licence
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 You are able to provide your own Mocks in BeanTest to test external dependencies
Grouping Allows organizing tests in groups	No
Other Other useful information about the testing framework