freshyo/docs/test-cases/delivery-operations.md
2026-10-11 18:21:24 +05:30

2.3 KiB

Delivery sequence and operational maps

Scope: slot deliverySequence, admin delivery order/map views and order coordinate overrides. Fixtures: A/B orders, addresses with/without coordinates, split siblings.

ID Priority Action / input Expected result
DELIVERY-01 P1 Set/reorder A slot's delivery sequence. Saved exact intended order; reload and operational list agree.
DELIVERY-02 P1 Update order operational coordinates. Correct order marker moves; customer identity/region/bound unchanged.
DELIVERY-03 P1 Empty sequence, one order, many addresses. Meaningful map/list and deterministic order.
DELIVERY-04 P0 A sequence contains B order or wrong slot's order. Unauthorized/incoherent association rejected.
DELIVERY-05 P1 Duplicate/missing/cancelled order IDs. Validated/reconciled; no duplicate stop or cancelled demand.
DELIVERY-06 P1 New order arrives after sequence saved. Defined insertion/unsequenced handling; no silently hidden delivery.
DELIVERY-07 P1 Cancel/deliver order while delivery view open. List/map/status refresh coherently; route doesn't resurrect stale stop.
DELIVERY-08 P0 Invalid lat/lng/nonfinite/out-of-range coordinate. Rejected; previous operational coordinates retained.
DELIVERY-09 P1 Address lacks coordinates or multiple orders share address. Useful warning/distinct order association; no arbitrary marker.
DELIVERY-10 P0 Customer/anonymous/B admin alters A coordinates/sequence. Forbidden; no order/address write.
DELIVERY-11 P1 Coordinate override vs customer subsequently edits address. Approved ownership/snapshot policy, no silent customer-bound mutation.
DELIVERY-12 P1 Concurrent reorder/update and network failure. Coherent saved sequence, recoverable UI; no lost unrelated stop.
DELIVERY-13 P2 Map load failure, offline tiles, zoom/resize/back. List remains usable; loading bounded, address data not exposed externally unnecessarily.
DELIVERY-14 P1 Orders split across slots at same address. Correct slot-specific stops/quantities; no group double-count confusion.

Policy checkpoint: delivery sequence schema, unsequenced new-order placement, and operational versus customer address-coordinate ownership.