
Migrate legacy dsvm functional test jobs for python-glanceclient to the project repository as zuul3 jobs using the devstack functional base job. Co-authored-by: Monty Taylor <mordred@inaugust.com> Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com> Needed-By: I0b974bf60da6bafabeb037a75ac10654e2a6406c Needed-By: I0271a1430843ef546e991a7a3c4b572b3e404963 Depends-On: I84de60181cb88574e341ff83cd4857cce241f2dd Change-Id: I1977ee0d348645987107c2efb5b454d7f8b81adf
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