Files

Monty Taylor 84538d8870 Use clouds.yaml from devstack for functional tests

devstack produces a file called clouds.yaml already with credentials in
it. Rather than producing our own config file to run functional tests,
just consume the clouds.yaml file that's already there.

Closes-Bug: #1507386
Change-Id: I82c071b2cd903b9578d1f2ec515882c815812692

2015-10-21 05:43:26 +09:00

hooks

Use clouds.yaml from devstack for functional tests

2015-10-21 05:43:26 +09:00

__init__.py

Create functional test base

2015-04-18 17:43:01 +00:00

base.py

Use clouds.yaml from devstack for functional tests

2015-10-21 05:43:26 +09:00

README.rst

Create functional test base

2015-04-18 17:43:01 +00:00

test_readonly_glance.py

Use clouds.yaml from devstack for functional tests

2015-10-21 05:43:26 +09:00

README.rst

python-glanceclient functional testing

Idea

Run real client/server requests in the gate to catch issues which are difficult to catch with a purely unit test approach.

Many projects (nova, keystone...) already have this form of testing in the gate.

Testing Theory

Since python-glanceclient 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