Frontend-html: E2E tests - workflow step-path assertions fail on Windows (`/` vs `\`)

What version of Origam are you using: branch mobx-react-upgrade


Hi all,

Running the frontend e2e suite (test/tests_e2e) locally on Windows, 9 of the
workflow tests in 09_workflow.test.js fail, while the suite is green on the
Linux CI.

It’s a path-separator mismatch. The tests assert the workflow error message with
startsWith, hard-coding a forward slash in the step path, e.g.:

Merge context 'AllDataTypes', Step 'Basic WF_1stepfail/0100_StepFail' failed.

but the actual message uses the OS-native separator, so on Windows it contains a
backslash:

...Step 'Basic WF_1stepfail\0100_StepFail' failed.

The split is clean: every failing test asserts a message containing a
WF_.../NNNN_StepFail path; the tests that assert only "Fail Step" (no path)
all pass.

Why it matters: it makes the e2e suite effectively Linux-only and adds noise for
contributors running it locally on Windows.

Proposal: normalise the separator in the waitForWorkflowMessage helper before comparing (replace \ with / in the actual message), which keeps the assertion OS-agnostic. A backend fix to always emit / is the alternative, but the
test-side change is smaller and lower-risk.

Thanks!