blob: 1b285745e0f6df8a21b651ff74086da9188199ae (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
=========
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-doc:`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.
__ https://git.openstack.org/cgit/openstack/governance/tree/reference/project-testing-interface.rst
|
