At the moment we show this warning if we call to a tool from the parent env:
WARNING: test command found but not installed in testenv
cmd: /home/ob/.virtualenvs/play/bin/pytest
env: /home/ob/do/play/.tox/python
Maybe you forgot to specify a dependency? See also the whitelist_externals envconfig setting.
I am working on documentation improvements for #461 and my current feeling is that we should start throwing an error if somebody does not whitelist an external command from tox 4 on. From 3.7 on we should show an enhanced warning that will announced that the warning will be an error from tox 4 on - like:
WARNING: test command found but not installed in testenv
cmd: /home/ob/.virtualenvs/play/bin/pytest
env: /home/ob/do/play/.tox/python
Maybe you forgot to specify a dependency? See also the whitelist_externals envconfig setting.
DEPRECATION WARNING: this will be an error in tox 4 and above
At the moment we show this warning if we call to a tool from the parent env:
I am working on documentation improvements for #461 and my current feeling is that we should start throwing an error if somebody does not whitelist an external command from tox 4 on. From 3.7 on we should show an enhanced warning that will announced that the warning will be an error from tox 4 on - like: