openstack
/
python-novaclient
Code Issues Proposed changes
python-novaclient/novaclient/tests/functional
History
Jenkins 9e15b3d7c0 Merge "[Bug-Fix] Update requests body for quota-update" 2015-09-04 17:33:13 +00:00
..
api add ips to novaclient server manager 2015-04-21 12:40:53 -04:00
hooks Update path to subunit2html in post_test_hook 2015-09-02 19:08:09 -07:00
README.rst Add functional testing README 2015-03-09 14:41:02 -07:00
__init__.py First pass at tempest_lib based functional testing 2015-01-28 15:44:43 -08:00
base.py Merge "Add method for better random name" 2015-08-31 22:07:08 +00:00
clouds.yaml.sample Add a sample clouds.yaml 2015-06-15 17:53:21 +00:00
fake_crypto.py Adds support for x509 certificates as keypairs 2015-08-05 19:55:48 +00:00
test_instances.py Merge "Add method for better random name" 2015-08-31 22:07:08 +00:00
test_keypairs.py fix novaclient functional tests for new devstack config 2015-09-03 13:19:28 -04:00
test_quotas.py [Bug-Fix] Update requests body for quota-update 2015-09-04 17:49:27 +03:00
test_readonly_nova.py Adding missing nova read only CLI test 2015-06-08 03:25:56 -07:00
test_servers.py Add mechanism to vm list to return all resources 2015-08-27 12:48:05 +03:00
test_volumes_api.py Add method for better random name 2015-08-31 17:05:13 +03:00

README.rst

python-novaclient functional testing

Idea

Over time we have noticed two issues with novaclient unit tests.

  • Does not exercise the CLI
  • We can get the expected server behavior wrong, and test the wrong thing.

We are using functional tests, run against a running cloud (primarily devstack), to address these two cases.

Additionally these functional tests can be considered example uses of python-novaclient.

These tests started out in tempest as read only nova CLI tests, to make sure the CLI didn't simply stacktrace when being used (which happened on multiple occasions).

Testing Theory

We are treating python-novaclient as legacy code, so we do not want to spend a lot of effort adding in missing features. In the future the CLI will move to python-openstackclient, and the python API will be based on the OpenStack SDK project. But until that happens we still need better functional testing, to prevent regressions etc.

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