Mistral workflows should be unit tested

Registered by Dougal Matthews

The logic in our workflows is growing and becoming more complex over time. We cover the "happy" path for a number of workflows in CI, but our error handling is generally untested (or only manually tested). We can partially resolve this by running the Mistral workflows in a Python unit test with mocked actions. Allowing us to execute all of the branches in a workflow.

There is a similar bug, regarding running the workflows with tempest. A combination of both of these approaches will create the best result. https://bugs.launchpad.net/bugs/1733869

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
Accepted for future
Implementation:
Deferred
Milestone target:
None

Related branches

Sprints

Whiteboard

[2018-07-32] Moving to Stein. If this is needed for Rocky please request an FFE with justification.

A POC patch can be found here: https://review.openstack.org/553389

Gerrit topic: https://review.openstack.org/#q,topic:425060,n,z (not sure where this came from? seems unrelated)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.