nose
nose copied to clipboard
nose-devs
nose is nicer testing for python
``` $ nosetests -v -s --cover-html --cover-html-dir=htmlcov --cover-erase --with-coverage --cover-package=lib --logging-filter=root lib/security/* test_get_external_customer_id (tests.lib.security.partners.test_grs.TestGrsAuth) ... ok test_validate_expiration_false (tests.lib.security.partners.test_grs.TestGrsAuth) ... ok test_validate_expiration_true (tests.lib.security.partners.test_grs.TestGrsAuth) ... ok test_validate_required_fields_false (tests.lib.security.partners.test_grs.TestGrsAuth) ... ok test_validate_required_fields_true (tests.lib.security.partners.test_grs.TestGrsAuth)...
What steps will reproduce the problem? 1. Run xunit unit test w/ --processes=2 2. See fails What is the expected output? What do you see instead? All of nose's tests...
The docstring contains escape sequences (`\b`, `\.`) in regular expressions that should not be interpreted by the Python lexer.
Running nosetests with the `--cover-min-percentage` flag on a skeleton package with only an \_\_init\_\_.py file fails because the coverage output does not include a total line. ``` $ python setup.py...
Unicode does not pass through in my tests that are using captured stdout. Example: ``` # -*- encoding: utf-8 -*- import unittest class test(unittest.TestCase): def test_unicode(self): print u'» unicode' assert...
setup.py wants to put the man page in ${PREFIX}/man/man1, but that's only right some of the time. We need to figure out how to find the man prefix for the...
There are several printed messages, skips and runtime errors that make more sense when the name of the test is listed. --- This change is [](https://reviewable.io/reviews/nose-devs/nose/996)
This change is [](https://reviewable.io/reviews/nose-devs/nose/995)
The pip --use-mirrors option was deprecated in version 1.5, and removed in 7.0, and 7.1.2 is now included with Travis' Python 3.5.0 environment. Travis automatically installs packages in requirements.txt if...
`LazySuite` will, by default, keep a cache of tests that are being added to it. This cache never gets removed, so when running a very large test suite, older test...
