openstack/mistral-tempest-plugin
Code Issues Proposed changes
825f5d06a7
mistral-tempest-plugin/mistral_tempest_tests
History
Andras Kovi e6e8f61c2e Use id of workflow instead of name to keep track of what is created 
With concurrent test executions it is possible that namespaced and
non-namespaced tests run at the same time, making it flaky whether
the name of the workflow is enough to identify the workflow. Using
the id should work in all cases.

Change-Id: Ib0e7d31f9a983c723704b64b1c46940aace545d7
2018-07-19 09:48:30 +02:00
..
services Use id of workflow instead of name to keep track of what is created 2018-07-19 09:48:30 +02:00
tests Use id of workflow instead of name to keep track of what is created 2018-07-19 09:48:30 +02:00
__init__.py Initial layout for mistral tempest plugin. 2015-12-24 06:11:06 +00:00
config.py Stop adding ServiceAvailable group option 2016-10-01 13:50:30 +05:30
plugin.py Stop adding ServiceAvailable group option 2016-10-01 13:50:30 +05:30
README.rst Added README.rst file for tempest plugin. 2015-12-24 06:14:12 +00:00

README.rst

Tempest Integration of Mistral

This directory contains Tempest tests to cover the mistral project.

To list all Mistral tempest cases, go to tempest directory, then run:

$ testr list-tests mistral

To run only these tests in tempest, go to tempest directory, then run:

$ ./run_tempest.sh -N -- mistral

To run a single test case, go to tempest directory, then run with test case name, e.g.:

$ ./run_tempest.sh -N -- mistral_tempest_tests.tests.api.v2.test_mistral_basic_v2.WorkbookTestsV2.test_get_workbook

Alternatively, to run mistral tempest plugin tests using tox, go to tempest directory, then run:

$ tox -eall-plugin mistral

And, to run a specific test:

$ tox -eall-plugin mistral_tempest_tests.tests.api.v2.test_mistral_basic_v2.WorkbookTestsV2.test_get_workbook