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

Nose

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

Artos

https://www.theartos.com/
Programming language

Python

Java

Category

Unit Testing, unittest Extensions

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

Artos is an opensource BDD testing framework for writing Unit, Intergration and Functional tests

Artos includes pre-configured logging framework and extent reports, utilities to write flow for manual/semi-automated testing and supports BDD testing using cucumber scripts.
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

Yes

It is a xUnit style framework
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

With Artos you can perform unit tests on front-end components
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 unit test server side behaviours and functionalities by testing specific back-end classes and functions
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.

N/A

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.

N/A

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

You can use a third party library like mockito
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

Artos allows creation of test suites and they are run by use of a test script
Other
Other useful information about the testing framework