OpenStack Testing (Tempest) of an existing cloud
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
tempest/tempest/tests
Zuul 34432dc970 Merge "Modify the response example in test_subnetpools_client" 10 months ago
..
api [part1] Remove six 2 years ago
cmd Remove unicode from code 2 years ago
common Merge "Add floating IP waiter" 10 months ago
files Change openstack-dev to openstack-discuss 4 years ago
lib Merge "Modify the response example in test_subnetpools_client" 10 months ago
README.rst Doc: fix markups, capitalization and add 2 REVIEWING advices 5 years ago
__init__.py
base.py Use unittest.mock instead of third party mock 2 years ago
fake_config.py Add test coverage CMD cleanup_service 4 years ago
fake_tempest_plugin.py Service Clients registration interface for plugins 6 years ago
test_base_test.py Support scope in dynamic cred for specific roles 2 years ago
test_config.py Revert "Move dscv and ca_certs to config section service_clients" 6 years ago
test_decorators.py Remove deprecated test.idempotent_id decorator 2 years ago
test_hacking.py Update hacking for Python3 3 years ago
test_imports.py Use unittest.mock instead of third party mock 2 years ago
test_list_tests.py [part1] Remove six 2 years ago
test_microversions.py [part1] Remove six 2 years ago
test_tempest_plugin.py Add a validation resources fixture 5 years ago
test_test.py Moving API microversion fixture in resource_setup 10 months ago
utils.py

README.rst

Tempest Field Guide to Unit tests

What are these tests?

Unit tests are the self checks for Tempest. They provide functional verification and regression checking for the internal components of Tempest. They should be used to just verify that the individual pieces of Tempest are working as expected. They should not require an external service to be running and should be able to run solely from the Tempest tree.

Why are these tests in Tempest?

These tests exist to make sure that the mechanisms that we use inside of Tempest are valid and remain functional. They are only here for self validation of Tempest.

Scope of these tests

Unit tests should not require an external service to be running or any extra configuration to run. Any state that is required for a test should either be mocked out or created in a temporary test directory. (see test_wrappers.py for an example of using a temporary test directory)