openstack
/
python-novaclient
Code Issues Proposed changes
python-novaclient/novaclient/tests/functional
History
Takashi Natsume 437d63de29 Add a cleanup for a server in a functional test 
A VM instance is created in the following functional test.

* novaclient.tests.functional.v2.test_instance_action.
  TestInstanceActionCLIV262.test_show_actions_with_host

However the VM instance is not deleted after the functional test.
Add a cleanup for the server in the functional test.

Change-Id: I8c2a6f91739d50baa283b37b16de67c542ea691b
Closes-Bug: #1889283
Signed-off-by: Takashi Natsume <takanattie@gmail.com>
(cherry picked from commit 1ce9edcd73)
 		2020-07-29 17:00:17 +00:00
..
api Remove deprecated network APIs 2017-04-03 13:17:25 -04:00
hooks Switch legacy Zuul jobs to native Zuul v3 jobs 2020-07-10 23:56:21 +09:00
v2 Add a cleanup for a server in a functional test 2020-07-29 17:00:17 +00:00
README.rst Fix running functional tests against deployment with insecure SSL 2016-02-08 17:51:47 +01:00
__init__.py First pass at tempest_lib based functional testing 2015-01-28 15:44:43 -08:00
base.py Switch legacy Zuul jobs to native Zuul v3 jobs 2020-07-10 23:56:21 +09:00
clouds.yaml.sample Update clouds.yaml.sample 2016-07-11 15:53:55 -04:00
test_auth.py Switch legacy Zuul jobs to native Zuul v3 jobs 2020-07-10 23:56:21 +09:00

README.rst

python-novaclient functional testing

Idea

Over time we have noticed two issues with novaclient unit tests.

  • Does not exercise the CLI
  • We can get the expected server behavior wrong, and test the wrong thing.

We are using functional tests, run against a running cloud (primarily devstack), to address these two cases.

Additionally these functional tests can be considered example uses of python-novaclient.

These tests started out in tempest as read only nova CLI tests, to make sure the CLI didn't simply stacktrace when being used (which happened on multiple occasions).

Testing Theory

We are treating python-novaclient as legacy code, so we do not want to spend a lot of effort adding in missing features. In the future the CLI will move to python-openstackclient, and the python API will be based on the OpenStack SDK project. But until that happens we still need better functional testing, to prevent regressions etc.

Since python-novaclient has two uses, CLI and python API, we should have two sets of functional tests. CLI and python API. The python API tests should never use the CLI. But the CLI tests can use the python API where adding native support to the CLI for the required functionality would involve a non trivial amount of work.

Functional Test Guidelines

  • Consume credentials via standard client environmental variables:

    OS_USERNAME
OS_PASSWORD
OS_TENANT_NAME
OS_AUTH_URL

  • Usage of insecure SSL can be configured via the standard client environment variable:

    OS_INSECURE

  • Try not to require an additional configuration file