openstack/tempest
Code Issues Proposed changes
7a39bc1551
tempest/setup.cfg

52 lines
2.0 KiB
INI
Raw Normal View History

Migrate to pbr from openstack.common.setup. Change-Id: Ia85bda060a6c62c721b9104b2bd52d3fe1673367
2013-04-28 18:22:59 -07:00
[metadata]
name = tempest
summary = OpenStack Integration Testing
setup.cfg: Replace dashes with underscores Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I532be460dc673548be9ed3b540e9feb8ca832fbe Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
2021-03-18 10:38:50 +00:00
description_file =
Migrate to pbr from openstack.common.setup. Change-Id: Ia85bda060a6c62c721b9104b2bd52d3fe1673367
2013-04-28 18:22:59 -07:00
README.rst
Fix author information I have checked the author of other projects. Most of them are just 'OpenStack'. And OpenStack QA is not suitable for the author because many development members contribute to Tempest. And author-email is not proper email address recently. It is deprecated now. Change-Id: I0f7405d107bf40d4781acb0e4b4a5db20d7606e4
2014-02-24 19:11:41 +09:00
author = OpenStack
setup.cfg: Replace dashes with underscores Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I532be460dc673548be9ed3b540e9feb8ca832fbe Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
2021-03-18 10:38:50 +00:00
author_email = openstack-discuss@lists.openstack.org
home_page = https://docs.openstack.org/tempest/latest/
Drop py3.6 and py3.7 from Tempest In zed cycle, OpenStack projects and oslo lib has dropped the py3.6 and py3.7 support - https://governance.openstack.org/tc/reference/runtimes/zed.html With oslo not supporting the py3.6 and py3.7, Tempest master is failing and cannot be run on py3.6|7 env. - https://bugs.launchpad.net/tempest/+bug/1975036 We discussed about how to solve it in ML[1] and QA meeting[2] and decided to drop it from Tempest too. Stable branches testing from stable/victoria to stable/yoga (currently supported branch by Tempest master) can be tested on py3.8 or if cloud run those releases on py3.6 then Tempest can be run in virtual env with py38. Closes-Bug: #1975036 [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028622.html [2] https://meetings.opendev.org/irclogs/%23openstack-qa/%23openstack-qa.2022-05-24.log.html#t2022-05-24T15:31:51 Change-Id: Ie844887a798a006794729e733748ceaa5e06d2db
2022-05-28 19:00:24 -05:00
python_requires = >=3.8
Migrate to pbr from openstack.common.setup. Change-Id: Ia85bda060a6c62c721b9104b2bd52d3fe1673367
2013-04-28 18:22:59 -07:00
classifier =
Intended Audience :: Information Technology
Intended Audience :: System Administrators
Intended Audience :: Developers
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
Programming Language :: Python
Add py34 to readme, pkg metadata, and envlist This commit adds references explaining the current state of python 3.4 and tempest to the readme, pkg metadata, and adds an etry to the tox envlist for running the unit tests on python 3.4. Change-Id: I9c1e3cdf53dbae723a9fee67ad96932709d2305f
2015-05-11 22:18:00 -04:00
Programming Language :: Python :: 3
Switch testing to Victoria testing runtime Updating the testing template from ussuri to victoria testing runtime - https://governance.openstack.org/tc/reference/runtimes/victoria.html Change-Id: If964909a73a52836e3adbb7b695f1c7322b81830
2020-05-04 14:16:54 -05:00
Programming Language :: Python :: 3.8
Fix python classifier for py39 Temepest test and support python 3.9 so fixing then python classifier in setup.cfg Change-Id: Ida4ca6e04f6485c5c11e95ff708558267a827d2a
2022-11-23 14:33:00 -06:00
Programming Language :: Python :: 3.9
Migrate tempest jobs to Ubuntu Jammy (22.04) As per 2023.1 cycle testing runtime and community goal[1] we need to migrate upstream CI/CD to Ubuntu Jammy(22.04). Most of the Tempest jobs will be migrate automatically once devstack base job start running on Jammy(Depends-On). As we need to run at least one job on Ubuntu Focal(20.04), I am adding a new job tempest-full-ubuntu-focal. Few job like tempest-full-multinode-py3 and plugin sanity job needs to override the nodeset. multinode job needs to run on Focal till stable/zed and on Jammy from master(2023.1) onwards. Stable branch jobs testing stable branch needs to keep running on their supported distro version which is Focal. Depends-On: https://review.opendev.org/c/openstack/devstack/+/860795 Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/861116 [1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html Change-Id: I2e37603b098880b778100613800496b01167b22f
2022-10-12 15:50:28 -05:00
Programming Language :: Python :: 3.10
Add python 3.11 unit test job Python 3.11 is going to be added as required python version testing[1] so testing it in advance is good idea. [1] https://governance.openstack.org/tc/reference/runtimes/2024.1.html#python-runtimes-for-2024-1 Change-Id: I77c51657d67b644ece30589f26bb795929f25bc4
2023-08-22 19:02:50 -07:00
Programming Language :: Python :: 3.11
[ussuri][goal] Drop python 2.7 support and testing OpenStack is dropping the py2.7 support in ussuri cycle. Tempest is ready with python 3 and ok to drop the python 2.7 support. Last Tempest version officially supported for py2.7 is 23.0.0. Now onwards, Tempest will test all stable branch with py3 jobs. tempest-full and other py2 version of jobs definition are kept for stable branch gate. Complete discussion & schedule can be found in - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html - https://etherpad.openstack.org/p/drop-python2-support Ussuri Communtiy-wide goal: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html Change-Id: I75868d5c9b6630fe78958ff89e58a0aced09a6b3
2020-02-04 09:04:30 -06:00
Programming Language :: Python :: 3 :: Only
Programming Language :: Python :: Implementation :: CPython
Migrate to pbr from openstack.common.setup. Change-Id: Ia85bda060a6c62c721b9104b2bd52d3fe1673367
2013-04-28 18:22:59 -07:00
Enable tempest install to setup a config dir This commit adds the necessary bits to tempest's setup.cfg file to instruct pbr on how to make sure that the sample config files and a /etc/tempest dir get setup when installing tempest. In the new cli workflow it is expected that by default /etc/tempest will exist as a source for local working dir configs. Partially implements: bp tempest-cli-improvements Change-Id: I2bf93f6789601caaebdfb85ac2b9f34b82f87980
2015-07-06 16:05:57 -04:00
[files]
packages =
tempest
data_files =
Use relative path in data_files in setup.cfg The absolute path causes failures when installing in a virtual environment, not having root privileges. This change solves the installation in a virtual environment, but it does not fix yet the tempest init workflow when installing into a virtual environment. Partially-fixes bug #1480389 Change-Id: Iddefb8db77ffe35a84fb35b6f9e7e823de4ab45f
2015-07-31 17:55:38 +01:00
etc/tempest = etc/*
Enable tempest install to setup a config dir This commit adds the necessary bits to tempest's setup.cfg file to instruct pbr on how to make sure that the sample config files and a /etc/tempest dir get setup when installing tempest. In the new cli workflow it is expected that by default /etc/tempest will exist as a source for local working dir configs. Partially implements: bp tempest-cli-improvements Change-Id: I2bf93f6789601caaebdfb85ac2b9f34b82f87980
2015-07-06 16:05:57 -04:00
Add cmd entry point for verify_tempest_config This commit moves the verify_tempest_config script from the tools dir to tempest.cmd and adds a pbr entry point for the script. This means that the script will in effect be a packaged binary for tempest. Partially implements bp config-verification Change-Id: I75b9743a8117d55c6c445db05eb39404b5708624
2014-04-23 20:35:49 +00:00
[entry_points]
console_scripts =
Add cliff based common cli entrypoint This commit adds the basic framework to tempest for a unified modular CLI endpoint using cliff. As of right now this entry-point doesn't really do anything but exist. It will be expanded in the future first all the existing commands will be refactored to be used through this. Secondly a new interface and workflow for running tempest will be created on top of this. Co-Authored-By: Matthew Treinish <mtreinish@kortar.org> Change-Id: I1ff8d22c120dbc81d812f1f107db7c2d9b15a505 Implements: blueprint tempest-cli-improvements
2015-04-02 01:27:34 -04:00
tempest = tempest.cmd.main:main
Use tempest.lib code in tempest Now that tempest_lib code is copied back into tempest, stop using tempest_lib in tempest, and start using the copied code. Remove the dependency to tempest_lib from requirements, and drop the script to use tempest_lib in tempest. Add os-testr to the test-requirements. Partially implements bp tempest-lib-reintegration Change-Id: I21ab5fe6349f72c98ac9f960a29bf62e813f8b1b
2016-02-23 14:07:24 -05:00
skip-tracker = tempest.lib.cmd.skip_tracker:main
check-uuid = tempest.lib.cmd.check_uuid:run
Add subunit-describe-calls Adds new command subunit-describe-calls, documentation, and unittests. subunit-describe-calls is a parser for subunit v1 & v2 streams to determine what REST API calls are made inside of a test and in what order they are called. Later commits will add additional functionality relating to request & response headers & body data along with a stdout output option and stdin input. Change-Id: I468d0d3e3b6098da95a81cc86d9bdd1b47ee1f03
2016-05-24 15:57:35 -05:00
subunit-describe-calls = tempest.cmd.subunit_describe_calls:entry_point
Add tempest init command to tempest cli This commit adds a new 'tempest init' command to the unified cli. This command tempest init will be the first step of the new workflow for running tempest. It is used to initilize a local working directory to run tempest from. The idea being you can setup different local working dirs for different tempest envs to test against several different clouds. The basic idea for this new workflow after installing tempest is something like: 1. mkdir tempest-newcloud 2. cd tempest-newcloud 3. tempest init 4. edit local config file 5. tempest run The next step after this is to start working on the 'tempest run' command. (which will include the hooks for the tempest plugin interface) But, until that is added a test runner can be called directly inside a local tempest working directory. Partially Implements bp tempest-cli-improvements Change-Id: I572267e61ba8ca86f92299e174864a7a89597207
2015-06-30 15:32:34 -04:00
tempest.cm =
Migrate tempest-account-generator to new cliff cli framework Leave existing endpoint for now as to not disrupt existing workflows and deprecate next cycle. Add deprication warning for old usage. Change-Id: I9db27a853184126a7f751800bc8cacd7dd4e40fd Implements: blueprint tempest-cli-improvements
2015-12-01 15:44:14 -08:00
account-generator = tempest.cmd.account_generator:TempestAccountGenerator
Added tempest subcommand for subunit_describe_calls We are adding a subcommand to tempest that is a parser for subunit streams to determine what REST API calls are made inside of a test and in what order they are called. Right now the implementation of utility is as a console script and which is in argparse. We are porting it to cliff to give a similar experience across the codebase. Change-Id: If95042898d8b2a148246c991d73d1a577fbcf7a0 Signed-off-by: Soniya Vyas <svyas@redhat.com>
2019-11-11 11:48:35 +05:30
subunit-describe-calls = tempest.cmd.subunit_describe_calls:TempestSubunitDescribeCalls
Add tempest init command to tempest cli This commit adds a new 'tempest init' command to the unified cli. This command tempest init will be the first step of the new workflow for running tempest. It is used to initilize a local working directory to run tempest from. The idea being you can setup different local working dirs for different tempest envs to test against several different clouds. The basic idea for this new workflow after installing tempest is something like: 1. mkdir tempest-newcloud 2. cd tempest-newcloud 3. tempest init 4. edit local config file 5. tempest run The next step after this is to start working on the 'tempest run' command. (which will include the hooks for the tempest plugin interface) But, until that is added a test runner can be called directly inside a local tempest working directory. Partially Implements bp tempest-cli-improvements Change-Id: I572267e61ba8ca86f92299e174864a7a89597207
2015-06-30 15:32:34 -04:00
init = tempest.cmd.init:TempestInit
Add cleanup to cliff-based cli framework Also disable ability to run script in stand-alone mode so users will use 'tempest cleanup' instead. Change-Id: I2119acd402b0985d4a81c85501ce7265f782d37b Implements: blueprint tempest-cli-improvements
2015-10-29 20:15:04 -07:00
cleanup = tempest.cmd.cleanup:TempestCleanup
Add tempest-list-plugins Add the tempest-list-plugins cmd. bp list-plugins Change-Id: If28311bc2e8d29a97ee46d7d73edba2a93aed7ce
2015-11-30 18:12:25 +00:00
list-plugins = tempest.cmd.list_plugins:TempestListPlugins
Migrate verify-tempest-config to new cliff cli framework Leave existing endpoint for now as to not disrupt existing workflows and deprecate next cycle. Added deprecation message for old entry point. Change-Id: If8afab441f51e5cf0f3bf1e2b95d76b2c1d0c474 Implements: blueprint tempest-cli-improvements
2015-11-18 16:12:27 -08:00
verify-config = tempest.cmd.verify_tempest_config:TempestVerifyConfig
Use cliff.lister for tempest workspace command This commit makes tempest workspace command use cliff.lister to show various formats. And this commit splits the original class - TempestWorkspace into the subcommand classes to use the cliff.lister class. With this splitting, we can get the subcommand helps as a side effect. Change-Id: I07c69c467743a2f132c99d992773a53bda3bec7b
2016-07-25 12:28:26 +09:00
workspace_register = tempest.cmd.workspace:TempestWorkspaceRegister
workspace_rename = tempest.cmd.workspace:TempestWorkspaceRename
workspace_move = tempest.cmd.workspace:TempestWorkspaceMove
workspace_remove = tempest.cmd.workspace:TempestWorkspaceRemove
workspace_list = tempest.cmd.workspace:TempestWorkspaceList
Add tempest run command This commit adds a new run command to the unified cli endpoint. The intent here is for tempest to control it's own run story. This implements the basic runner and selection functionality to use the command, however it's not necessarily the end state of the command. The functionality in this patch is just a starting point to add the command and the basic functionality needed. It is starting with a limited feature set with the intent to add additional, more complex functionality in self contained patches after the command exists. Co-Authored-by: David Paterson <davpat2112@yahoo.com> Co-Authored-by: Stephen Lowrie <stephen.lowrie@rackspace.com> Partially-Implements bp tempest-run-cmd Depends-On: I09299043e536521d48dbe10632621138e3a366e0 Change-Id: I24588b5c00d005320e8719cf82b5dd95662572cf
2016-05-23 15:48:22 -04:00
run = tempest.cmd.run:TempestRun
Move tempest to oslo-config-generator Also fixes tempest reported bug with old generator in oslo-incubator, when identical options are registered in different groups. Change-Id: I274f48503c1b61ca09cabc8d8c50245ba1059943 Closes-bug: 1282887
2014-08-05 18:11:29 +00:00
oslo.config.opts =
tempest.config = tempest.config:list_opts
Copy Permalink