Files

kairat_kushaev 29fcefc67a Fix warnings in glanceclient README

README.rst file for functional tests and glanceclient itself
raises some warnings when passing these docs through REST
validator and build the doc:
- Need additional empty line to provide correct indent in
cloud.yaml example
- Title should be with the same length as overline.
The patch fixes these warnings.

Change-Id: I2e2ef6f838ee639d1a88256b6e321181a62cc76b

2016-02-01 13:15:01 +03: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

Fix warnings in glanceclient README

2016-02-01 13:15:01 +03: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