Nosehttps://nose.readthedocs.io/en/latest/ |
TwistedTrialhttps://twistedmatrix.com/trac/wiki/TwistedTrial |
|
|---|---|---|
| Programming language | Python | Python |
| Category |
Unit Testing, unittest Extensions
|
Unit Testing, unittest Extensions
|
| 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. |
Trial is a unit testing framework for Python built by Twisted Matrix labs Trial is composed of two parts: First is a command-line test runner, which can be run on plain Python unit tests and can do automated unit-test discovery across files, modules, or even arbitrarily nested packages. Second is a test library, derived from Python's 'unittest.TestCase' |
|
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 Front-end components can be tested for example adding a web front-end using simple twisted.web.resource.Resource objects |
|
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 Server-side behaviour can be tested with Trial, it has various functions for this in the twisted.web.Resource package |
|
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 Trial supports various fixture methods such as 'setUp()' and 'tearDown' functions fixture for normal semantics of setup, and teardown |
|
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 Methods like 'setUp()' allow for creation of group fixtures |
|
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 |
Through use of third party libraries like test-generator. |
|
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 Trial can access the mock library inbuilt in python for mocking purposes |
|
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 Trial allows tests to be grouped into test packages |
|
Other
Other useful information about the testing framework |
|
|
Knapsack Pro