5f887d851e
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
19 lines
1021 B
Plaintext
19 lines
1021 B
Plaintext
[DEFAULT]
|
|
test_command=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
|
|
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
|
|
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \
|
|
${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests} $LISTOPT $IDOPTION
|
|
|
|
test_id_option=--load-list $IDFILE
|
|
test_list_option=--list
|
|
# NOTE(cdent): The group_regex describes how testrepository will
|
|
# group tests into the same process when running concurently. The
|
|
# following insures that gabbi tests coming from the same YAML file
|
|
# are all in the same process. This is important because each YAML
|
|
# file represents an ordered sequence of HTTP requests. Note that
|
|
# tests which do not match this regex will not be grouped in any
|
|
# 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=nova\.tests\.functional\.api\.openstack\.placement\.test_placement_api(?:\.|_)([^_]+)
|