openstack
/
neutron
Code Issues Proposed changes

Update TOX_ENV_SRC_MODULES example 

TESTING.rst describes how to use TOX_ENV_SRC_MODULES
to use a local copy of library source code while
testing, but included pep8 when only unit testing
is supported.

Trivialfix

Change-Id: I133574c759d02843591e7448753d72cc4fd75491
This commit is contained in:
Brian Haley 2019-12-18 11:37:38 -05:00
parent 1e19349a16
commit d484bbec2e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
TESTING.rst
View File

@ -520,7 +520,7 @@ For example, to run against the 'master' branch of neutron-lib::
cd $SRC
git clone https://opendev.org/openstack/neutron-lib
cd $NEUTRON_DIR
env TOX_ENV_SRC_MODULES=$SRC/neutron-lib tox -r -e pep8,py37
env TOX_ENV_SRC_MODULES=$SRC/neutron-lib tox -r -e py37
To run against a change of your own, repeat the same steps, but use the
directory with your changes, not a fresh clone.
@ -533,7 +533,7 @@ desired gerrit refs for this example)::
cd neutron-lib
git fetch https://opendev.org/openstack/neutron-lib refs/changes/13/635313/6 && git checkout FETCH_HEAD
cd $NEUTRON_DIR
env TOX_ENV_SRC_MODULES=$SRC/neutron-lib tox -r -e pep8,py37
env TOX_ENV_SRC_MODULES=$SRC/neutron-lib tox -r -e py37
Note that the '-r' is needed to re-create the tox virtual envs, and will also
be needed to restore them to standard when not using this method.
@ -542,7 +542,7 @@ Any pip installable package can be overriden with this environment variable,
not just neutron-lib. To specify multiple packages to override, specify them
as a space separated list to TOX_ENV_SRC_MODULES. Example::
env TOX_ENV_SRC_MODULES="$SRC/neutron-lib $SRC/oslo.db" tox -r -e pep8,py37
env TOX_ENV_SRC_MODULES="$SRC/neutron-lib $SRC/oslo.db" tox -r -e py37
Functional Tests
~~~~~~~~~~~~~~~~