Allow for environmetal variables in testpaths

[gzpac]

It would be nice to be able to use environmental variables for testpaths parameters.

So that I could write:
testpaths = $MY_VIRTUAL_ENV/usr/lib64/python2.7/my_lib/ (coverage style)

or

testpaths = {env:MY_VIRTUAL_ENV}/usr/lib64/python2.7/my_lib/ (tox style)

pytest version: 3.2.1
python version: cpython 2.7
OS: opensuse 12

[pytestbot]

GitMate.io thinks possibly related issues are #241 (Allow for a forced xpass), #135 (allow to disable the asserts), #2382 (Allow customizing showlocals cutoff), #3403 (How to pass a variable from a test to another test), and #2435 (f).

[blueyed]

Doesn't $PYTEST_ADDOPTS work for you?
I.e. export PYTEST_ADDOPTS="-o testpaths=$MY_VIRTUAL_ENV/…"

[gzpac]

It doesn't because we have several project where we want to run pytest. Therefore we need to to define a configuration specific to a project.

[blueyed]

Check out https://github.com/Tarrasch/zsh-autoenv, https://github.com/direnv/direnv etc.

[RonnyPfannschmidt]

@gzpac this is pretty much a hack to set testpaths to a installed package name, instead of allowing env vars there i would rather have support to list an actual package name

then it would be something like

testpaths = --pyargs mylib

for example (we really should find a better way to spell it out tho)

[gzpac]

@RonnyPfannschmidt That would work for me. You can even constrain it to installed packages, i.e. something like
testpaths = --pylibs mylib

[nicoddemus]

@gzpac it seems your question have been answered so I'm closing this. Feel free to follow up with further questions though.