- nose extends the test loading and running features of unittest, making
it easier to write, find and run tests.
By default, nose will run tests in files or directories under the current working directory whose names include “test” or “Test” at a word boundary (like “test_this” or “functional_test” or “TestClass” but not “libtest”). Test output is similar to that of unittest, but also includes captured stdout output from failing tests, for easy print-style debugging.
These features, and many more, are customizable through the use of plugins. Plugins included with nose provide support for doctest, code coverage and profiling, flexible attribute-based test selection, output capture and more. More information about writing plugins may be found on in the nose API documentation, here: http://readthedocs.org/docs/nose/
If you have recently reported a bug marked as fixed, or have a craving for the very latest, you may want the development version instead: https://github.com/nose-devs/nose/tarball/master#egg=nose-dev
3 maintainers
Release files for nose 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nose-1.3.0.tar.gz | 404.9 kB | Details |
Release files / nose-1.3.0.tar.gz
| Download URL | nose-1.3.0.tar.gz |
|---|---|
| Size | 404.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e63cc3325de75cf98ffad40be72fa69753de824695173178f74c034fe4f5260
|
|
BLAKE2b-256 checksum How to use checksums |
def4b205776cf5cbddbc1e2c3223fa29c0d05f18a9b8afad8cfa23438c217434
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
