Mistral workflows should be unit tested
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:/
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
- Started by
- Completed by
Related branches
Related bugs
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:/
Gerrit topic: https:/