RETIRED, further work has moved to Debian project infrastructure
Go to file
kurt grandis 1035878324 Merge pull request #14 from cclauss/patch-1
Python 3.5 and 3.6
2017-02-01 06:57:40 -05:00
test_dirs futurize code also add ability to fetch a method's class depending on whether the system is py2 or py3 2015-06-25 02:51:42 -04:00
.gitignore updating authors, housecleaning, begin migration to github 2015-06-24 01:34:25 -04:00
.travis.yml Python 3.5 but NOT Python3.6 2017-01-30 19:53:08 +01:00
AUTHORS bump version and contributors 2016-09-06 14:12:29 -04:00
COPYRIGHT updating authors, housecleaning, begin migration to github 2015-06-24 01:34:25 -04:00
LICENSE explicitly adding copyright and licensing files along with 'authors' 2011-10-16 18:38:09 -04:00
MANIFEST.in snapshot of 0.1.10 2015-06-24 00:53:32 -04:00
README.rst Merge pull request #8 from millerdev/exclude-tests-env 2016-09-06 14:06:41 -04:00
nose_exclude.py Merge pull request #8 from millerdev/exclude-tests-env 2016-09-06 14:06:41 -04:00
setup.py bump version and contributors 2016-09-06 14:12:29 -04:00
tests.py Merge pull request #8 from millerdev/exclude-tests-env 2016-09-06 14:06:41 -04:00
tox.ini Update tox.ini 2017-01-30 00:36:52 +01:00

README.rst

Overview

nose-exclude is a Nose plugin that allows you to easily specify directories to be excluded from testing.

Exclude Directories

The --exclude-dir= option is made available after installation of the plugin. The option may be used multiple times to exclude multiple directories from testing. The directory paths provided may be absolute or relative.

Example:

$ nosetests --exclude-dir=test_dirs/build \
    --exclude-dir=test_dirs/test_not_me test_dirs
....
----------------------------------------------------------------------
Ran 4 tests in 0.006s

OK

This example will exclude the directories test_dirs/build and test_dirs/test_not_me from nosetests' test searching.

Using File-Based Exclusion List

The --exclude-dir-file= option can be used to pass in a predefined list of directories contained within a file. nose-exclude expects each directory to be excluded to be on its own line.

Example:

$ nosetests --exclude-dir-file=test_dirs/exclude_dirs.txt \
    test_dirs
....
----------------------------------------------------------------------
Ran 4 tests in 0.006s

OK

where exclude_dirs.txt might look like: :

test_dirs/build
# Start a line with a '#' to include
# Comments
test_dirs/test_not_me

Excluding Specific Test Methods and Classes

Tests can now be excluded by specifying their fully qualified test paths. Tests can be excluded using either --exclude-test or --exclude-test-file.

To exclude test methods:

--exclude-test=module1.module2.TestClass.test_method

To exclude test classes:

--exclude-test=module1.module2.TestClass

To exclude test functions:

--exclude-test=module1.module2.test_function

Using Environment Variables

--exclude-dir= and --exclude-test= can be set by the environment variables NOSE_EXCLUDE_DIRS and NOSE_EXCLUDE_TESTS respectively. Multiple exclude paths may be entered by separating them using a ;. The environment variable NOSE_EXCLUDE_DIRS_FILE when set to the path of a file-based exclusion list functions as though it were passed in with --exclude-dir-file=.

Nose Configuration Files

nose-exclude options can also be passed to nosetests using a .noserc or nose.cfg file. If you more than one directory are to be excluded separate their values with newlines using the same configuration key: :

[nosetests]
exclude-dir=test_dirs/exclude_dirs
            test_dirs/more_excludes

Bugs

Please report all bugs (and patches) to https://github.com/kgrandis/nose-exclude/

NOTE: The previous bitbucket repository is no longer actively maintained.