Original task (#158): /my-orders has a useEffect cleanup that, on
unmount, clears every still-running undo timer and immediately fires
the deletions for whatever IDs were queued. This unmount-flush path
was previously not covered by tests — only the "Undo" path was.
Implementation:
- New spec: artifacts/tx-os/tests/order-delete-flush-on-unmount.spec.mjs
- Mirrors the test scaffolding (DB pool, user/order seeding, login,
language init, toast locator) used by the existing order-undo-toast
and order-clear-finished-undo specs.
- Flow: seed a completed order, log in, go to /my-orders, click trash
+ "Yes, delete" to queue the deletion, then navigate away via the
in-page Back button (which is wouter setLocation("/services") — an
in-SPA route change, so MyOrdersPage actually unmounts and the
cleanup useEffect runs).
- Asserts both required outcomes from the task spec:
* A DELETE /api/orders/:id request is observed during the
navigation (with a 2xx response).
* The order row is actually gone from the DB.
- Additionally records the timestamp of the DELETE request and asserts
it fires within 3s of the navigation (well under UNDO_WINDOW_MS).
This guards against a regression that removes the cleanup but
accidentally still passes because the natural 7s timer eventually
fires anyway in the SPA — without the cleanup, the DELETE would
arrive ~7s later and the assertion would time out.
- Clean up the seeded order id from the afterAll list when the test
successfully deletes it via the UI, so teardown does not try to
re-delete a missing row.
No production code changed; this is a pure test addition.
Replit-Task-Id: 655f3d3b-5fc5-4a87-a754-76ec67148186
riyadhafraa
40534b7c8f