Test cases & workflow versions

Test cases are saved per workflow version. This page explains what happens to your test cases when you modify a workflow, and how to get them ready to run again.

How versioning works

• Each workflow version keeps its own set of test cases.
• When you modify a workflow and proceed to testing, all existing test cases move to Error status — review and re-save each one to bring it back to Ready to Test.
• You can also run test cases for the currently published version through its view-only mode, independent of the draft you're editing.

How workflow changes affect test cases

Any change to the workflow — editing a node's configuration or form, adding a node, deleting a node, or replacing one node with another — moves all existing test cases for that version to Error status. This applies regardless of whether the changed node was mocked in the test case.

The test case itself is not lost: the mock configuration stored against each node is retained, and the test case stays in your list in Error status until you review it.

Bringing a test case back to Ready

1. Open the test case in Error status. Each screen of its configuration shows the errors on that screen, and Save & Continue is blocked, so you fix the errors and move to the next screens.
2. Review each screen against the updated workflow and fix anything flagged — for example, update mocks on nodes whose configuration changed, or provide values for newly added mandatory form fields.
3. Save the test case. Once every screen is resolved, its status returns to Ready to Test and it can be run again.