keystone/.testr.conf
Brant Knudson 0c407c5f8d Keystoneclient tests from venv-installed client
The keystoneclient tests were using the library installed from a
git clone. Rather than do a clone of master, the tests will now just
use the keystoneclient installed to the venv.

Doing a `git clone` causes problems on any system without reliable
Internet access, and since the keystoneclient tests have changed to
being for functional tests rather than for verifying
backwards-compatibility of the client, this will make things easier.

Change-Id: I079fa77501b8987a4724d03a792b084a6d853e21
2015-01-08 16:11:15 -06:00

20 lines
713 B
Plaintext

[DEFAULT]
test_command=
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} \
${PYTHON:-python} -m subunit.run discover -t ./ ./keystone/tests $LISTOPT $IDOPTION
test_id_option=--load-list $IDFILE
test_list_option=--list
group_regex=.*(test_cert_setup)
# NOTE(morganfainberg): If single-worker mode is wanted (e.g. for live tests)
# the environment variable ``TEST_RUN_CONCURRENCY`` should be set to ``1``. If
# a non-default (1 worker per available core) concurrency is desired, set
# environment variable ``TEST_RUN_CONCURRENCY`` to the desired number of
# workers.
test_run_concurrency=echo ${TEST_RUN_CONCURRENCY:-0}