diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/source/data/tempest-non-active-plugins-registry.header (renamed from doc/source/data/tempest-blacklisted-plugins-registry.header) | 4 | ||||
| -rw-r--r-- | doc/source/overview.rst | 2 | ||||
| -rw-r--r-- | doc/source/stable_branch_support_policy.rst | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/doc/source/data/tempest-blacklisted-plugins-registry.header b/doc/source/data/tempest-non-active-plugins-registry.header index 6b6af1147..06d8eaa93 100644 --- a/doc/source/data/tempest-blacklisted-plugins-registry.header +++ b/doc/source/data/tempest-non-active-plugins-registry.header @@ -1,7 +1,7 @@ -Blacklisted Plugins +Non Active Plugins =================== List of Tempest plugin projects that are stale or unmaintained for a long -time (6 months or more). They can be moved out of blacklist state once one +time (6 months or more). They can be moved out of nonactivelist state once one of the relevant patches gets merged: https://review.opendev.org/#/q/topic:tempest-sanity-gate+%28status:open%29 diff --git a/doc/source/overview.rst b/doc/source/overview.rst index e51b90b96..2eaf72f18 100644 --- a/doc/source/overview.rst +++ b/doc/source/overview.rst @@ -113,7 +113,7 @@ as it is simpler, and quicker to work with. There is also the option to use `stestr`_ directly. For example, from the workspace dir run:: - $ stestr run --black-regex '\[.*\bslow\b.*\]' '^tempest\.(api|scenario)' + $ stestr run --exclude-regex '\[.*\bslow\b.*\]' '^tempest\.(api|scenario)' will run the same set of tests as the default gate jobs. Or you can use `unittest`_ compatible test runners such as `stestr`_, `pytest`_ etc. diff --git a/doc/source/stable_branch_support_policy.rst b/doc/source/stable_branch_support_policy.rst index 87e3ad1e8..9c2d1ed66 100644 --- a/doc/source/stable_branch_support_policy.rst +++ b/doc/source/stable_branch_support_policy.rst @@ -20,7 +20,7 @@ Tempest from master as long as possible. But, because we won't be actively testing branches in these phases, it's possible that we'll introduce changes to Tempest on master which will break support on *Extended Maintenance* phase branches. When this happens the expectation for those branches is to either -switch to running Tempest from a tag with support for the branch, or blacklist +switch to running Tempest from a tag with support for the branch, or exclude a newly introduced test (if that is the cause of the issue). Tempest will not be creating stable branches to support *Extended Maintenance* phase branches, as the burden is on the *Extended Maintenance* phase branche maintainers, not the Tempest |