openstack
/
tempest
Code Issues Proposed changes
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.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0ea2c01d75'
${ noResults }
tempest/tempest/tests
History
zhufl 0ea2c01d75
Break wait_for_volume_resource_status when error_extending 		4 years ago
..
api Set max_microversion 2.35 for nova image tests 5 years ago
cmd Checking config file actually exist or not in tempest run 4 years ago
common Break wait_for_volume_resource_status when error_extending 4 years ago
files Change openstack-dev to openstack-discuss 4 years ago
lib Merge "Add APIMicroversionFixture to library interface" 4 years ago
README.rst Doc: fix markups, capitalization and add 2 REVIEWING advices 6 years ago
__init__.py Add unittest framework + tests for wrapper scripts 10 years ago
base.py Improve patch and patchobject Base test case method attributes. 5 years ago
fake_config.py Add test coverage CMD cleanup_service 5 years ago
fake_tempest_plugin.py Service Clients registration interface for plugins 7 years ago
test_base_test.py Default to using neutron networks_client in get_tenant_network 5 years ago
test_config.py Revert "Move dscv and ca_certs to config section service_clients" 7 years ago
test_decorators.py Remove deprecated skip decorators 6 years ago
test_hacking.py Add autopep8 to tox.ini 4 years ago
test_imports.py Add unit tests to check for CONF getattr during import 6 years ago
test_list_tests.py Mark raw strings as such 5 years ago
test_microversions.py Unsupported 'message' Exception attribute in PY3 6 years ago
test_tempest_plugin.py Add a validation resources fixture 6 years ago
test_test.py Add unit tests for not overriding setUpClass 6 years ago
utils.py Unit tests: mock some time.sleep and time.time 7 years ago

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)