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

Test::Unit

https://test-unit.github.io/

Nose

https://nose.readthedocs.io/en/latest/
Programming language

Ruby

Python

Category

Unit Testing, Intergration Testing

Unit Testing, unittest Extensions

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

Nose is a Python unit test framework

This is a Python unit test framework that intergrates well with doctests, unnittests, and 'no-boilerplate tests', that is tests written from scratch without a specific boilerplate.
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

nose is a unit testing tool which is very similar to unittest. It is basically unittest with extensions therefore just like unittest is can test front-end components and behaviour
Server-side
Allows testing the bahovior of a server-side code

Yes

Yes

Nose can test back-end components and functionality as small units. One can write tests for each function that provides back-end functionality
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

Yes

nose supports fixtures at the package, module, class, and test case levels, so that initialization which can be expensive is done as infrequently as possible.
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

Yes

Group fixtures are allowed with nose, where a multitest state can be defined.
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

Through use of third party libraries like test-generator and from the 'unittest.TestCase' library
Licence
Licence type governing the use and redistribution of the software

LGPLv2.1, Ruby Licence

GNU Library or Lesser General Public License (LGPL) (GNU LGPL)

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

The nose library extends the built-in Python unittest module therefore has access to unittest.mock
Grouping
Allows organizing tests in groups

No

Yes

With nose it collects tests automatically and there’s no need to manually collect test cases into test suites.
Other
Other useful information about the testing framework