UI Tests for Workflow Always Nodes

[dsesami]

ISSUE TYPE

• Test cases

COMPONENT NAME

• UI

SUMMARY

UI Testing for #2373

Test cases:

• Ensure that an “always” node can be be the parent, sibling, or child of a success, failure, or another “always” node, and that the UI displays this correctly.
• Ensure that root nodes are always set to “always”.
• Ensure that without siblings, the UI has all three options selectable.
• Ensure that editing nodes with/without siblings of each type allows for selection of all types.
  - [ ] Ensure that the UI responds appropriately when a cycle could be created with the combination of an always node with success or failure nodes. (Expected behavior?) (can't be done by design it seems)
• Ensure that “always” nodes appear and disappear with regular operations on workflows.
  Deletion of nodes shifts the workflow “upstream” if it is in the middle of the workflow:
• Ensure that this does not cause some sort of restriction violation and that the operation is allowed, that all options are visible.
• Ensure that the “shifted” child node can be edited freely.