1d9322a2f5
Update doc links according to OpenStack document migration Change-Id: I189f2b31456203c80234a44cbf87534f8c159ed0
29 lines
866 B
ReStructuredText
29 lines
866 B
ReStructuredText
=========
|
|
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.
|
|
|
|
``tox -e functional``
|
|
|
|
Live functional testing against an existing OpenStack instance.
|
|
|
|
Functional testing assumes the existence of a `clouds.yaml` file as supported
|
|
by `os-client-config <https://docs.openstack.org/os-client-config/latest>`__
|
|
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.
|
|
|
|
__ https://git.openstack.org/cgit/openstack/governance/tree/reference/project-testing-interface.rst
|