
We have a lot of Tempest public interfaces which are used by the tempest plugins and sometime it is not easy to know breaking changes as we do not test all plugins test when any change merge in Tempest. Example: https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/937725 To avoid these breaking changes at some extend, let's run the cinder tempest plugin tests in one of the Temp[est job. Evantually, we can add more plugins tests if needed but I think cinder-tempest-plugin uses a good amount of interfaces. Change-Id: I80c2b77936ac3220ff05232877eaf6fbac4743a5
26 lines
997 B
Plaintext
26 lines
997 B
Plaintext
# This file includes the list of tests which need to be
|
|
# excluded to run from integrated testing (tempest-full job
|
|
# or other generic jobs. We will run these tests in a separate
|
|
# jobs. This is needed to avoid the job timeout, details in
|
|
# bug#2004780.
|
|
# Basic criteria to add test in this list is:
|
|
# * Admin test which are not needed for interop and most of them
|
|
# are running as part of other API and Scenario tests.
|
|
# * Negative tests which are mostly covered in tempest API tests
|
|
# or service unit/functional tests.
|
|
|
|
# All admin tests except keystone admin test which might not have much
|
|
# coverage in existing other tests
|
|
tempest.api.compute.admin
|
|
tempest.api.volume.admin
|
|
tempest.api.image.admin
|
|
tempest.api.network.admin
|
|
|
|
# This also run cinder-tempest-plugin tests so that we can avoid any
|
|
# breaking change to plugins (cinder-tempest-plugins uses most of the
|
|
# Tempest interface) but we can add more plugins tests here if needed.
|
|
cinder_tempest_plugin
|
|
|
|
# All negative tests
|
|
negative
|