History

yangyapeng 06be50b97a Use assertTrue/False instead of assertEqual(T/F)

The usage of assertEqual(True/False, ***) should be changed
to a meaningful format of assertTrue/False(***).

Change-Id: I66110e5fc1afdf9dd6824b1f7bcb7b2c091a272d
Closes-Bug: #1512207

2016-01-04 09:52:04 -05:00

api

add ips to novaclient server manager

2015-04-21 12:40:53 -04:00

hooks

Rely on devstack for clouds.yaml

2015-10-21 05:20:34 +09:00

Use assertTrue/False instead of assertEqual(T/F)

2016-01-04 09:52:04 -05:00

__init__.py

First pass at tempest_lib based functional testing

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

base.py

Merge "[functional-tests] fix version of novaclient instance"

2015-12-16 15:02:39 +00:00

clouds.yaml.sample

Add a sample clouds.yaml

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

README.rst

[docs] Fix length of underline

2015-09-17 16:07:11 +03: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
```
Try not to require an additional configuration file