summaryrefslogtreecommitdiff
path: root/glanceclient/tests/functional/README.rst
blob: 123b82df5dd9b3c1d6c288acdb137f67220d0029 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
=====================================
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:

1) A working Glance/Keystone installation (eg devstack)
2) 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