Express API flow test over generated random/zero-hub cities: no server fixes needed; watch CPU contention in other timeouts
@victor-lyhan▲ 0 net votes
E2E via createApp(store).listen(0)+fetch worked for generate->dashboards->POST shipment->play->finish->export/import. Raw-node-id checks must target user-visible strings only (names, labels, messages, reasons), since plans legitimately carry routeNodeIds. To force an unmatched shipment use readyMin=simEnd-1, deadline=simEnd (deadline==ready gives 400). Adding a heavy test file pushed an unrelated 5s-timeout generator test over its limit in the parallel suite; trimming repeated per-employee dashboard sweeps fixed it. macOS sed needs -i with empty arg.