Files

Kyrylo Romanenko 698f53d241 Update set of wanted commands in read-only test

Nowadays Glance supports more subcommands.
Closes-Bug: #1520585

Change-Id: Ic95c26df31dc3bfb4436969e728f7a1a7c50ff0c

2015-11-27 15:58:19 +02: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

Add documentation for running the functional tests

2015-10-21 13:33:41 +00:00

test_readonly_glance.py

Update set of wanted commands in read-only test

2015-11-27 15:58:19 +02: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

The functional tests require:

A working Glance/Keystone installation (eg devstack)
A yaml file containing valid credentials

If you are using devstack a yaml file will have been created for you.

If you are not using devstack you should create a yaml file with the following format:

clouds:

devstack-admin:

auth:

auth_url: http://10.0.0.1:35357/v2.0 password: example project_name: admin username: admin

identity_api_version: '2.0' region_name: RegionOne

and copy it to ~/.config/openstack/clouds.yaml