c8f3a65549
1.What is the purpose of this patch set? The Tricircle project doesn't provide integration test yet. To achieve integration test, the Tricircle needs to provide Tempest plugin, so that the integration test job could be configured in CI pipeline. Tempest is a set of integration tests to be run against a live OpenStack cluster: http://docs.openstack.org/developer/tempest/overview.html Tempest has an external test plugin interface which enables project to integrate an external test suite as part of a tempest run. http://docs.openstack.org/developer/tempest/plugin.html This patch set is to create the Tricircle tempest plugin with a sample test case. And main purpose of the patch set is to make tempest enable to discover the Tricircle tempest plugin and its test case. 2.What is the benefit of this patch set for the Tricircle project? Make the Tricircle tempest plugin being able to be discovered by Tempest, and support later integration test job. 3.What is the platform you tested it out? It will work on all linux distribution including python venv, docker container are available. The procedure to make discovering processes are as follows: Install the Tricircle after the patch merged (the Tricircle tempest plugin and the sample tempest test case will be installed together for they are in the same repository): 1. git clone https://github.com/openstack/tricircle.git 2. sudo pip install -e tricircle/ Install the Tempest in another folder in order to avoid the python import error: 1. git clone https://github.com/openstack/tempest.git 2. sudo pip install -e tempest/ Then run testr in tempest folder to see if the test case of the Tricircle has been discovered: 1. cd tempest/ 2. testr list-tests | grep Tricircle The Tricircle devstack plugin is also updated with the Tricircle package installation in order to simplify the tempest discovering processes. Change-Id: I977c23f5e55e3ee062190fa9d5e6472e5d5acb33 Signed-off-by: Chaoyi Huang <joehuang@huawei.com>
8 lines
337 B
Plaintext
8 lines
337 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:-60} \
|
|
${PYTHON:-python} -m subunit.run discover $TRICIRCLE_TEST_DIRECTORY $LISTOPT $IDOPTION
|
|
test_id_option=--load-list $IDFILE
|
|
test_list_option=--list
|