E2E Bot Test 002 — Full UI + API Integration

Run ID: run-verify-e2e-bot-002-20260316-1306 | 2026-03-16 13:06 | Order: PZ-TEST-BOT-161008

Overall: PASS (8/8)

Test Results

BlockDescriptionStatus
V1-BOTOrder notification in ops-alertsPASS
V2-BOTRoute channel createdPASS
V3-BOTClient support chatPASS
V4-BOTClient order threadPASS
V5Support historyPASS
V6Token proxyPASS
V7-BOTRoute completion notificationPASS
UI-DISPDispatcher UI viewsPASS

Details

V1-BOT: Order Notification

Order PZ-TEST-BOT-161008 created via SQL. Bot posted notification to #ops-alerts within 5s.

V2-BOT: Route Channel

Route created, bot created private channel route-20260317-k-2788. Welcome post with technician info. Members auto-added: evcharge-bot, dmitriy.k, test.dispatcher.

V3-BOT: Support Chat

POST /bot/chat/support returned 200 with channelId=support-9967723c. Message appeared in MM support channel.

V4-BOT: Order Thread

POST /bot/chat/order returned 200 with threadId. DB record in mm_order_thread confirmed.

V5: Support History

GET /bot/chat/support/history returned 3 messages. Bug from bot-001 run (502) is now fixed.

V6: Token Proxy

GET /bot/chat/token returned 26-char MM token. Dispatcher JWT auth accepted.

V7-BOT: Route Completion

Route set to COMPLETED. Bot posted completion notification with archive timer (17.03.2026 13:12).

UI-DISP: Dispatcher Views

Dashboard: order PZ-TEST-BOT-161008 visible. Routes list: route 27884113 visible with status "Завершен", technician "К Дмитрий".

Test Data

OrderPZ-TEST-BOT-161008
Route ID27884113-5f64-4c5f-ab80-160fe6e4927c

Observation: /bot/health endpoint times out (curl exit 28). All functional endpoints work.

Back to index