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

Nose

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

TestNG

https://testng.org/doc/documentation-main.html
Programming language

Python

Java

Category

Unit Testing, unittest Extensions

Unit Testing, Intergration Testing, End-to-End 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.

TestNG is a testing framework for the Java programming language inspired by JUnit and NUnit

TestNG is similar to JUnit and NUnit but with newer functionalities such as: annotations, test that your code is multithread safe, flexible test configuration, support for data-driven testing (with @DataProvider), support for parameters, powerful execution model (no more TestSuite) and more... It's also designed to cover all categories of tests unit, functional, end-to-end, intergration... etc
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

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

The scope of testing with testNg is wide and you can test various front-end functionalities and behaviours with it
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 server-side functionalities and behaviours with TestNg
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

Fixtures are inbuilt into testNG, these are the annotations which are: @BeforeSuite, @AfterSuite, @BeforeTest, @AfterTest, @BeforeGroups, @AfterGroups, @BeforeClass, @AfterClass, @BeforeMethod, @AfterMethod
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

You can use various fixtures to setup environments for group tests
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)

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)

Yes

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

Yes

By Use of an external library like mockit which intergrates well with testNG
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

Multiple test cases can be grouped more easily by converting them into testng.xml file, in which you can make priorities which test case should be executed first
Other
Other useful information about the testing framework