[-c CONFIGFILE] [-e envlist] [--notest] [--sdistonly]
[--installpkg PATH] [--develop] [-i URL] [--pre] [-r]
[--result-json PATH] [--hashseed SEED] [--force-dep REQ]
[--sitepackages] [--skip-missing-interpreters]
[args [args ...]]
tox options
positional arguments:
args additional arguments available to command positional
substitution
optional arguments:
--version report version information to stdout.
-h, --help show help about options
--help-ini, --hi show help about ini-names
-v increase verbosity of reporting output.
--showconfig show configuration information for all environments.
-l, --listenvs show list of test environments
-c CONFIGFILE use the specified config file name.
-e envlist work against specified environments (ALL selects all).
--notest skip invoking test commands.
--sdistonly only perform the sdist packaging activity.
--installpkg PATH use specified package for installation into venv,
instead of creating an sdist.
--develop install package in the venv using 'setup.py develop'
via 'pip -e .'
-i URL set indexserver url (if URL is of form name=url set
the url for the 'name' indexserver, specifically)
--pre install pre-releases and development versions of
dependencies. This will pass the --pre option to
install_command (pip by default).
-r, --recreate force recreation of virtual environments
--result-json PATH write a json file with detailed information about all
commands and results involved.
--hashseed SEED set PYTHONHASHSEED to SEED before running commands.
Defaults to a random integer in the range [1,
4294967295] ([1, 1024] on Windows). Passing 'noset'
suppresses this behavior.
--force-dep REQ Forces a certain version of one of the dependencies
when configuring the virtual environment. REQ Examples
'pytest<2.7' or 'django>=1.6'.
--sitepackages override sitepackages setting to True in all envs
--skip-missing-interpreters
don't fail tests for missing interpreters
Environment variables
TOXENV: comma separated list of environments (overridable by '-e')
TOX_TESTENV_PASSENV: space-separated list of extra environment variables to be passed into test command environments
there is no tox-instruments for your case
so we need to do smth custom
maybe "set -e && tox" ?
need to discuss that
@rkhozinov
there is no tox-instruments for your case
so we need to do smth custom maybe "set -e && tox" ? need to discuss that @rkhozinov