nose extends unittest to make testing easier
- 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://somethingaboutorange.com/mrl/projects/nose/
If you have recently reported a bug marked as fixed, or have a craving for the very latest, you may want the unstable development version instead: http://bitbucket.org/jpellerin/nose/get/tip.gz#egg=nose-dev
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size nose-1.0.0-py3.1.egg (326.6 kB)||File type Egg||Python version 3.1||Upload date||Hashes View|
|Filename, size nose-1.0.0.tar.gz (718.8 kB)||File type Source||Python version None||Upload date||Hashes View|