[placement] Adjust the name of the gabbi tests
Recently there was some confusion caused by the fact the gabbi tests used by the placement API have names like this: gabbi.suitemaker.test_placement_api_usage_create_provider This means that the names cannot be matched against tox interactions like: tox -efunctional -- nova.tests.functional.api.openstack This change makes it so the tests are generated with names like: nova.tests.functional.api.openstack.placement.test_placement_api.usage_create_provider So this change is submitted for review if people care. The other option is to: tox -efunctional placement gabbi was updated to allow this functionality in a clean form, so this depends on a change to global requirements but can work without it if required. Depends-On: Ie93c0e680a80fc7f157e2b5b9dfc2ab17f934f10 Change-Id: I8579bf7529a7298c4d049e47cc3cde1731a5e666
This commit is contained in:
parent
d4b35152c0
commit
5f887d851e
|
@ -15,4 +15,4 @@ test_list_option=--list
|
|||
# special way. See the following for more details.
|
||||
# http://testrepository.readthedocs.io/en/latest/MANUAL.html#grouping-tests
|
||||
# https://gabbi.readthedocs.io/en/latest/#purpose
|
||||
group_regex=(gabbi\.(?:driver|suitemaker)\.test_placement_api_([^_]+))
|
||||
group_regex=nova\.tests\.functional\.api\.openstack\.placement\.test_placement_api(?:\.|_)([^_]+)
|
||||
|
|
|
@ -23,5 +23,6 @@ def load_tests(loader, tests, pattern):
|
|||
"""Provide a TestSuite to the discovery process."""
|
||||
test_dir = os.path.join(os.path.dirname(__file__), TESTS_DIR)
|
||||
return driver.build_tests(test_dir, loader, host=None,
|
||||
test_loader_name=__name__,
|
||||
intercept=fixtures.setup_app,
|
||||
fixture_module=fixtures)
|
||||
|
|
|
@ -24,7 +24,7 @@ testtools>=1.4.0 # MIT
|
|||
tempest-lib>=0.14.0 # Apache-2.0
|
||||
bandit>=1.1.0 # Apache-2.0
|
||||
openstackdocstheme>=1.5.0 # Apache-2.0
|
||||
gabbi>=1.24.0 # Apache-2.0
|
||||
gabbi>=1.25.0 # Apache-2.0
|
||||
|
||||
# vmwareapi driver specific dependencies
|
||||
oslo.vmware>=2.11.0 # Apache-2.0
|
||||
|
|
Loading…
Reference in New Issue