History

zhengyao1 0c64947c6f make string.letters python3 compatible

The string.letters in python2 was supported. But in python3,
string.letters was removed. In python3, recommend using
string.ascii_letters instead. This patch fix it.

Change-Id: I7bfe2b94c0c740d9143ddddc655f8086a537f24b
Closes-Bug: #1595786

2016-06-24 18:53:53 +08:00

api

Allow to specify a network for functional tests

2016-02-16 12:43:04 +01:00

hooks

Make functional tests work with v3 keystone

2016-04-12 17:24:41 +03:00

make string.letters python3 compatible

2016-06-24 18:53:53 +08:00

__init__.py

First pass at tempest_lib based functional testing

2015-01-28 15:44:43 -08:00

base.py

Added functional tests for server tags (microverison 2.26)

2016-06-15 21:13:38 +03:00

clouds.yaml.sample

Add a sample clouds.yaml

2015-06-15 17:53:21 +00:00

README.rst

Fix running functional tests against deployment with insecure SSL

2016-02-08 17:51:47 +01:00

test_auth.py

Fix funtional test gate failure caused by keystone client change.

2016-05-27 09:18:01 +08: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