History

Anna Babich f6e0dcd34c Functional tests for flavors with public and non-public access

The added tests check granting access actions for public and
non-public flavors

The test for microversion 2.7 checks that the appropriate
error is returned when attempting to grant an access
to a public flavor for the given tenant

The base TenantTest class has been added to avoid code
duplication in test_keypairs and test_flavor_access tests

Also, test_keypairs code has been modified in accordance with
TenantTestBase class usage

Change-Id: Icf21d8aceaa191aee8b8ffc7c52e97ebe9509b3d

2016-01-19 16:14:55 +02: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

Functional tests for flavors with public and non-public access

2016-01-19 16:14:55 +02:00

__init__.py

First pass at tempest_lib based functional testing

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

base.py

Functional tests for flavors with public and non-public access

2016-01-19 16:14:55 +02: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