-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add a directory whitelist option #694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type: enhancement
new feature or API change, should be merged into features branch
Comments
Original comment by BitBucket: thiefmaster, GitHub: thiefmaster: I agree. Specifying a folder or file manually should always override the |
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Jul 9, 2015
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Jul 9, 2015
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Jul 9, 2015
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Jul 9, 2015
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Jul 10, 2015
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this issue
Jul 10, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by: BitBucket: thiefmaster, GitHub: thiefmaster
Right now you can only blacklist directories using
norecursedirs
. However, especially in larger projects, it might be much nicer to simply whitelist the folders where you know that there are or might be tests.Another advantage of this would be avoiding collisions with people creating virtualenvs e.g. in
projectfolder/env
(personally I always addenv*
tonorecursedirs
, but what if someone uses a different folder for his environment?).Actually, it might make sense if pytest detected virtualenv folders and automatically skipped them...
The text was updated successfully, but these errors were encountered: