e2c89f777d
* Introduced new class Workflow that manages life-cycle of running workflows and is responsible for managing workflow persistent state * Moved all workflow level logic to workflow handler and Workflow class * Changed semantics if how workflows start errors are handled. Previously, in case of invalid user input Mistral engine would store information about error in "state_info" field of workflow execution and bubble up an exception to the user. This approach was incorrect for a number of reasons including broken semantics: if an exception was raised due to invalid input it's normal to expect that system state has not changed. After this refactoring, engine only raises an exception in case of bad user input. That way behavior is consistent with the idea of exceptional situations. * Fixed unit tests in according to the previous point * Fixed a number of logical issues in tests. For example, in test_default_engine.py we expected one type of errors (e.g. env not found) but effectively received another one (invalid input). Partially implements: blueprint mistral-engine-error-handling Change-Id: I09070411fd833df8284cb80db69b8401a40eb6fe |
||
---|---|---|
.. | ||
services | ||
tests | ||
__init__.py | ||
plugin.py | ||
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