| 1 |
Testing |
| 2 |
|
| 3 |
The preferred way to run the unit tests is using ``tox``. There are multiple |
| 4 |
test targets that can be run to validate the code. |
| 5 |
|
| 6 |
``tox -e pep8`` |
| 7 |
Style guidelines enforcement. |
| 8 |
|
| 9 |
``tox -e py37`` |
| 10 |
Traditional unit testing (Python 3.7). |
| 11 |
|
| 12 |
``tox -e cover`` |
| 13 |
Generate a coverage report on unit testing. |
| 14 |
|
| 15 |
Functional testing assumes the existence of a `clouds.yaml` file as supported |
| 16 |
by `os-client-config <https://docs.openstack.org/os-client-config/latest>`__ |
| 17 |
It assumes the existence of a cloud named `devstack` that behaves like a normal |
| 18 |
DevStack installation with a demo and an admin user/tenant - or clouds named |
| 19 |
`functional_admin` and `functional_nonadmin`. |
| 20 |
|
| 21 |
Refer to `Consistent Testing Interface`__ for more details. |
| 22 |
|
| 23 |
__ https://opendev.org/openstack/governance/src/branch/master/reference/project-testing-interface.rst |
| 24 |
|
| 25 |
Refer to `Tester Use`__ for more details. |
| 26 |
|
| 27 |
__ https://wiki.openstack.org/wiki/Testr |