{"id":28524106,"url":"https://github.com/cloudbase/lis-tempest","last_synced_at":"2025-07-29T03:05:58.596Z","repository":{"id":20825611,"uuid":"24111494","full_name":"cloudbase/lis-tempest","owner":"cloudbase","description":"LIS OpenStack Tempest tests ","archived":false,"fork":false,"pushed_at":"2014-09-16T19:34:44.000Z","size":11156,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":6,"default_branch":"master","last_synced_at":"2025-06-09T10:11:38.666Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/cloudbase.png","metadata":{"files":{"readme":"README.rst","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-09-16T18:09:48.000Z","updated_at":"2014-09-16T18:29:29.000Z","dependencies_parsed_at":"2022-09-13T20:00:19.792Z","dependency_job_id":null,"html_url":"https://github.com/cloudbase/lis-tempest","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/cloudbase/lis-tempest","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudbase%2Flis-tempest","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudbase%2Flis-tempest/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudbase%2Flis-tempest/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudbase%2Flis-tempest/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/cloudbase","download_url":"https://codeload.github.com/cloudbase/lis-tempest/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudbase%2Flis-tempest/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":267621581,"owners_count":24116900,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-07-29T02:00:12.549Z","response_time":2574,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-06-09T10:10:29.967Z","updated_at":"2025-07-29T03:05:58.589Z","avatar_url":"https://github.com/cloudbase.png","language":"Python","readme":"Tempest - The OpenStack Integration Test Suite\n==============================================\n\nThis is a set of integration tests to be run against a live OpenStack\ncluster. Tempest has batteries of tests for OpenStack API validation,\nScenarios, and other specific tests useful in validating an OpenStack\ndeployment.\n\nDesign Principles\n-----------------\nTempest Design Principles that we strive to live by.\n\n- Tempest should be able to run against any OpenStack cloud, be it a\n  one node devstack install, a 20 node lxc cloud, or a 1000 node kvm\n  cloud.\n- Tempest should be explicit in testing features. It is easy to auto\n  discover features of a cloud incorrectly, and give people an\n  incorrect assessment of their cloud. Explicit is always better.\n- Tempest uses OpenStack public interfaces. Tests in Tempest should\n  only touch public interfaces, API calls (native or 3rd party),\n  public CLI or libraries.\n- Tempest should not touch private or implementation specific\n  interfaces. This means not directly going to the database, not\n  directly hitting the hypervisors, not testing extensions not\n  included in the OpenStack base. If there is some feature of\n  OpenStack that is not verifiable through standard interfaces, this\n  should be considered a possible enhancement.\n- Tempest strives for complete coverage of the OpenStack API and\n  common scenarios that demonstrate a working cloud.\n- Tempest drives load in an OpenStack cloud. By including a broad\n  array of API and scenario tests Tempest can be reused in whole or in\n  parts as load generation for an OpenStack cloud.\n- Tempest should attempt to clean up after itself, whenever possible\n  we should tear down resources when done.\n- Tempest should be self testing.\n\nQuickstart\n----------\n\nTo run Tempest, you first need to create a configuration file that\nwill tell Tempest where to find the various OpenStack services and\nother testing behavior switches.\n\nThe easiest way to create a configuration file is to copy the sample\none in the ``etc/`` directory ::\n\n    $\u003e cd $TEMPEST_ROOT_DIR\n    $\u003e cp etc/tempest.conf.sample etc/tempest.conf\n\nAfter that, open up the ``etc/tempest.conf`` file and edit the\nconfiguration variables to match valid data in your environment.\nThis includes your Keystone endpoint, a valid user and credentials,\nand reference data to be used in testing.\n\n.. note::\n\n    If you have a running devstack environment, tempest will be\n    automatically configured and placed in ``/opt/stack/tempest``. It\n    will have a configuration file already set up to work with your\n    devstack installation.\n\nTempest is not tied to any single test runner, but testr is the most commonly\nused tool. After setting up your configuration file, you can execute\nthe set of Tempest tests by using ``testr`` ::\n\n    $\u003e testr run --parallel\n\nTo run one single test  ::\n\n    $\u003e testr run --parallel tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_reboot_non_existent_server\n\nAlternatively, you can use the run_tempest.sh script which will create a venv\nand run the tests or use tox to do the same.\n\nConfiguration\n-------------\n\nDetailed configuration of tempest is beyond the scope of this\ndocument. The etc/tempest.conf.sample attempts to be a self\ndocumenting version of the configuration.\n\nThe sample config file is auto generated using the script:\ntools/generate_sample.sh\n\nThe most important pieces that are needed are the user ids, openstack\nendpoints, and basic flavors and images needed to run tests.\n\nCommon Issues\n-------------\n\nTempest was originally designed to primarily run against a full OpenStack\ndeployment. Due to that focus, some issues may occur when running Tempest\nagainst devstack.\n\nRunning Tempest, especially in parallel, against a devstack instance may\ncause requests to be rate limited, which will cause unexpected failures.\nGiven the number of requests Tempest can make against a cluster, rate limiting\nshould be disabled for all test accounts.\n\nAdditionally, devstack only provides a single image which Nova can use.\nFor the moment, the best solution is to provide the same image uuid for\nboth image_ref and image_ref_alt. Tempest will skip tests as needed if it\ndetects that both images are the same.\n\nUnit Tests\n----------\n\nTempest also has a set of unit tests which test the tempest code itself. These\ntests can be run by specifing the test discovery path::\n\n    $\u003e OS_TEST_PATH=./tempest/tests testr run --parallel\n\nBy setting OS_TEST_PATH to ./tempest/tests it specifies that test discover\nshould only be run on the unit test directory. The default value of OS_TEST_PATH\nis OS_TEST_PATH=./tempest/test_discover which will only run test discover on the\ntempest suite.\n\nAlternatively, you can use the run_tests.sh script which will create a venv and\nrun the unit tests. There are also the py26, py27, or py33 tox jobs which will\nrun the unit tests with the corresponding version of python.\n\nPython 2.6\n----------\n\nTempest can be run with Python 2.6 however the unit tests and the gate\ncurrently only run with Python 2.7, so there are no guarantees about the state\nof tempest when running with Python 2.6. Additionally, to enable testr to work\nwith tempest using python 2.6 the discover module from the unittest-ext\nproject has to be patched to switch the unittest.TestSuite to use\nunittest2.TestSuite instead. See:\n\nhttps://code.google.com/p/unittest-ext/issues/detail?id=79\n\nBranchless Tempest Considerations\n---------------------------------\n\nStarting with the OpenStack Icehouse release Tempest no longer has any stable\nbranches. This is to better ensure API consistency between releases because\nthe API behavior should not change between releases. This means that the stable\nbranches are also gated by the Tempest master branch, which also means that\nproposed commits to Tempest must work against both the master and all the\ncurrently supported stable branches of the projects. As such there are a few\nspecial considerations that have to be accounted for when pushing new changes\nto tempest.\n\n1. New Tests for new features\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nWhen adding tests for new features that were not in previous releases of the\nprojects the new test has to be properly skipped with a feature flag. Whether\nthis is just as simple as using the @test.requires_ext() decorator to check\nif the required extension (or discoverable optional API) is enabled or adding\na new config option to the appropriate section. If there isn't a method of\nselecting the new **feature** from the config file then there won't be a\nmechanism to disable the test with older stable releases and the new test won't\nbe able to merge.\n\n2. Bug fix on core project needing Tempest changes\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nWhen trying to land a bug fix which changes a tested API you'll have to use the\nfollowing procedure::\n\n    - Propose change to the project, get a +2 on the change even with failing\n    - Propose skip on Tempest which will only be approved after the\n      corresponding change in the project has a +2 on change\n    - Land project change in master and all open stable branches (if required)\n    - Land changed test in Tempest\n\nOtherwise the bug fix won't be able to land in the project.\n\n3. New Tests for existing features\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nIf a test is being added for a feature that exists in all the current releases\nof the projects then the only concern is that the API behavior is the same\nacross all the versions of the project being tested. If the behavior is not\nconsistent the test will not be able to merge.\n\nAPI Stability\n-------------\n\nFor new tests being added to Tempest the assumption is that the API being\ntested is considered stable and adheres to the OpenStack API stability\nguidelines. If an API is still considered experimental or in development then\nit should not be tested by Tempest until it is considered stable.\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudbase%2Flis-tempest","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcloudbase%2Flis-tempest","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudbase%2Flis-tempest/lists"}