Competing commands and browser refresh

Verification Boundary

The journey drives the live console or public Accounting APIs for its own fixture records. Closing cases require the coordinator’s isolated acceptance environment and serialized execution. This examination reads the assertions without running the journey.

What This Suite Proves

Two browser tabs submit different commands and the suite expects one accepted run. It checks changed-command refusal, reloads the run page and records both possible outcomes of a cancellation racing job start.

What It Does Not Prove

The colleague-key case permits either acceptance or conflict. Cancellation racing job start can be inconclusive. These branches do not prove a mandatory requester-identity conflict or deterministic queued cancellation.

Real Dependencies and Test Doubles

The journey uses Accounting APIs and authenticated personas, with CRM and payment fixture setup where required. Browser cases use the real hosted console. Recorded database omissions and unavailable fault hooks remain limitations of the source suite.

Must Not Be Doubled

For live qualification, keep authorization, execution, financial effects and retained records real wherever the journey asserts them. Replacing these boundaries with demonstration responses would change what the suite can prove.