Nose vs NUnit comparison of testing frameworks
What are the differences between Nose and NUnit?

Nose

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

NUnit

https://nunit.org/
Programming language

Python

.NET

Category

Unit Testing, unittest Extensions

Unit Testing

General info

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.

NUnit is an open-source unit testing framework for Microsoft .NET.

NUnit was Initially ported from JUnit. Tests can be run from a console runner, within Visual Studio through a Test Adapter or through 3rd party runners. Tests can be run in parallel and has Strong support for data driven tests. Unit supports multiple platforms including .NET Core, Xamarin Mobile, Compact Framework and Silverlight.
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

Yes

Nunit is one of many programs in the xUnit family
Client-side
Allows testing code execution on the client, such as a web browser

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

Yes

You can test front-end components with NUnit since it is a Unit testing framework the application is isolated into diverse modules which are tested independently
Server-side
Allows testing the bahovior of a server-side code

Yes

Nose can test back-end components and functionality as small units. One can write tests for each function that provides back-end functionality

Yes

You can test back-end components with NUnit, it is a Unit testing framework hence the application is isolated into diverse modules which are tested independently
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

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.

Yes

NUnit contains the fixture methods SetUp to initialize your test environment and TearDown method to destroy a test environment
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 allowed with nose, where a multitest state can be defined.

Yes

Group fixtures are available in NUnit
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.

Through use of third party libraries like test-generator and from the 'unittest.TestCase' library

N/A

Licence
Licence type governing the use and redistribution of the software

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

MIT License

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)

Yes

The nose library extends the built-in Python unittest module therefore has access to unittest.mock

Yes

You can create mock objects using the third party library moq
Grouping
Allows organizing tests in groups

Yes

With nose it collects tests automatically and there’s no need to manually collect test cases into test suites.

Yes

You can group tests into suites with NUnit
Other
Other useful information about the testing framework