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

	Test::Unit https://test-unit.github.io/	Test’em https://github.com/testem/testem
Programming language	Ruby	JavaScript
Category	Unit Testing, Intergration Testing	Unit 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 Unit testing test runner for JavaScript Test'em is framework agnostic and has support for Jasmine, Qunit, Mocha and others through custom test framework adapters. It canalso run tests on all major browsers as well as Node and Phantomjs
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	It has an xUnit reporter
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
Server-side Allows testing the bahovior of a server-side code	Yes
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
Grouping Allows organizing tests in groups	No
Other Other useful information about the testing framework