EVCharge E2E — run-e2e-order-and-route-20260304-2049

Verifications (V1-V11)

V1: Client auth (phone + OTP)

V2: Order created (date, address, vehicle)

V3: Order data on view page

V4: Order on main page, status "Принят"

V5: Order in Dispatcher unassigned

V6: Route created (tech, vehicle, station, 3 pts)

V7: Route in "Активные маршруты"

V8: Technician sees route

V9: Technician accepts route

V10: Dispatcher status updated

V11: Client status (DB=ASSIGNED, UI unchanged)

Test Steps

#	Module	Block	Status	Duration	Details
1	Client	Auth + Order Creation	✅	10m 20s	Logged in via OTP. Created order PZ-0530: 5 Mar 14:00, ул. Демьяна Бедного 17к3, BYD/ATTO 3. Verified on main page and details.
2	DB	Checkpoint 1: Order	✅	2s	PZ-0530: status=NEW, address="улица Демьяна Бедного, 17к3", date=2026-03-05 14:00
3	Dispatcher	Verify Order + Create Route	✅	4m 28s	Found PZ-0530 in unassigned orders. Route created: tech=Виталий Чижов, vehicle=Сова 321, station=DimaTest, 3 route points. Status "Запланирован".
4	DB	Checkpoint 2: Route	✅	2s	Route 863d4505: status=PLANNED, technician=Виталий Чижов, start=2026-03-05 13:38
5	Technician	Auth + Accept Route	✅	12m 53s	Logged in as sova@test.com. Found route with PZ-0530. Accepted route (old route ea3f61dc cancelled first). Status: IN_PROGRESS.
6	Dispatcher	V10: Status Change	✅	15s	Route #863d4505 now shows "Выполняется" (was "Запланирован").
7	Client	V11: Realtime Status	⚠️	10s	DB status=ASSIGNED. Realtime event received (console confirmed). UI label still "Принят" — known issue.

DB Checkpoints

Checkpoint 1: Order Created

SELECT id, "orderNumber", status, "addressShort", "scheduledDate" FROM orders WHERE "orderNumber" = 'PZ-0530';

PASS id=5d1e9956, orderNumber=PZ-0530, status=NEW, addressShort="улица Демьяна Бедного, 17к3", scheduledDate=2026-03-05 14:00:00

Checkpoint 2: Route Created

SELECT r.id, r.status, r."idTechnician", r."plannedStartTime", e."firstName", e."lastName" FROM routes r JOIN employees e ON e.id = r."idTechnician" WHERE r.id IN (SELECT rp."idRoute" FROM route_points rp JOIN orders o ON o.id = rp."idOrder" WHERE o."orderNumber" = 'PZ-0530');

PASS id=863d4505, status=PLANNED, technician=Виталий Чижов, plannedStartTime=2026-03-05 13:38:00

Final Check: Order Status After Route Acceptance

SELECT "orderNumber", status FROM orders WHERE "orderNumber" = 'PZ-0530';

PASS orderNumber=PZ-0530, status=ASSIGNED (changed from NEW)

Screenshots (15 captured)

01 — Client: Main page after login

02 — Client: Vehicle selection

04 — Client: Order PZ-0530 created

05 — Client: Order visible on main page

06 — Client: Order details page

07 — Dispatcher: Order found in unassigned

08 — Dispatcher: Route creation form

09 — Dispatcher: Route created

10 — Dispatcher: Active routes

11 — Technician: Main page (routes list)

12 — Technician: Route details

13 — Technician: Route accepted

14 — Dispatcher: Route status "Выполняется"

15 — Client: Order status (DB=ASSIGNED, UI="Принят")

Notes

Blocker resolved: Old route ea3f61dc from 2026-03-02 test run was still IN_PROGRESS, preventing technician from accepting new route. Error: "Technician already has an active route." Resolved by cancelling old route via Dispatcher UI.

Known issue (V11): Client app maps both NEW and ASSIGNED order statuses to UI label "Принят" / "Выбираем лучшего техника". The DB status change (NEW → ASSIGNED) is confirmed, and the Supabase Realtime event was received (console log). However, the visual label does not change. This appears to be a Client app bug where the status-to-label mapping doesn't distinguish NEW from ASSIGNED.

Test Data