History

Yikun Jiang 5483be7fe7 Microversion 2.62 - Add host/hostId to instance action event Adds support for microversion 2.62 which adds ``host`` (hostname) and ``hostId`` (an obfuscated hashed host id string) fields to the instance action ``GET /servers/{server_id}/os-instance-actions/{req_id}`` API. The event column is already included in the result of "nova instance-action <server> <request-id>" command, therefore does not have any CLI or python API binding impacts in the client. Related nova API change: I2f8b4a12a088b9ed96b428eafde2e0c478fb1db5 Part of blueprint: add-host-to-instance-action-events Change-Id: Iee7e1a3a22249c98873aa96694fd4885916cd097		2018-04-27 15:37:39 +08:00
..
api	Remove deprecated network APIs	2017-04-03 13:17:25 -04:00
hooks	[ci] Use pseudo-random names for new resources	2017-11-23 16:52:04 +00:00
v2	Microversion 2.62 - Add host/hostId to instance action event	2018-04-27 15:37:39 +08: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	Fix AttributeError in getting a resource ID	2018-04-03 23:59:22 +00:00
clouds.yaml.sample	Update clouds.yaml.sample	2016-07-11 15:53:55 -04:00
test_auth.py	[CLI] Fix token auth type	2018-04-19 18:43:45 +00: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