This ensures we have version-specific references to other projects [1]. [1] https://docs.openstack.org/openstackdocstheme/latest/#external-link-helper Change-Id: I3b9db8b71c082dd5f8d0564a9cdfdb2fa6dc5ed6
1.1 KiB
Testing
The preferred way to run the unit tests is using tox.
There are multiple test targets that can be run to validate the
code.
tox -e pep8-
Style guidelines enforcement.
tox -e py27-
Traditional unit testing (Python 2.7).
tox -e py35-
Traditional unit testing (Python 3.5).
tox -e functional-
Live functional testing against an existing OpenStack instance. (Python 2.7)
tox -e functional-py35-
Live functional testing against an existing OpenStack instance. (Python 3.5)
tox -e cover-
Generate a coverage report on unit testing.
Functional testing assumes the existence of a clouds.yaml file as supported by os-client-config <>. It assumes
the existence of a cloud named devstack
that behaves like a normal DevStack installation with a demo and an
admin user/tenant - or clouds named functional_admin and functional_nonadmin.
Refer to Consistent Testing Interface for more details.