test(server-app): e2e multi-station KOT routing by khaira777 · Pull Request #1388 · FreeOpenSourcePOS/FloCafe

khaira777 · 2026-10-27T21:48:24Z

Intent

Implement and verify issue #1348 (test(server-app): end-to-end multi-station KOT routing from the waiter app) and open a PR targeting main without merging it:

Users asked whether orders sent from the waiter app (Server App) print to the right kitchen station printers.
In code:
frontend/src/app/server-standalone/page.tsx calls printKotForOrder after Send, which posts /api/printers/print-kot with no stationName (~L770-777, L959-963). It is proxied by main/server-app.ts ~L432.
main/routes/printers.ts ~L1226-1320: with no station, routeItemsToStations (~L1166) groups items by category station printer. Unmatched items go to the default Kitchen ticket.
However, nothing tests this end to end (frontend/e2e/server-app-ordering.spec.ts mocks print-kot, and tests/issue-134-station-routing.test.ts tests only the routing function).
Task & Acceptance Criteria:
Add an integration test that sends an order through the Server App path (main/server-app.ts POST /api/printers/print-kot -> forwardToMainApi -> main/routes/printers.ts), with two categories mapped to two station printers, plus unmatched items that fall back to the default Kitchen ticket, and asserts that separate KOT dispatches happen with the right items each.
Stub the physical printer dispatch layer (main/printers/thermal.ts / network send), NOT the route or forwarding layer.
The test fails if routing is bypassed (for example, everything goes to one ticket).
It is wired into package.json so npm run test:script-coverage passes.
Do not change production code unless the test exposes an actual bug in the requested flow.

What Changed

Added tests/server-app-station-routing.test.ts to verify end-to-end KOT printing through the Server App loopback proxy (POST /api/printers/print-kot -> forwardToMainApi -> main/routes/printers.ts) while stubbing only the physical network socket connection (net.Socket.prototype.connect) for configured printer IPs.
Asserted multi-station ESC/POS dispatch across mapped category station printers (Grill and Bar) and default Kitchen fallback for unmapped items, orderId-only reprints, delta item appends, inactive station fallback to the default Kitchen printer, and negative checks against single-ticket or cross-station routing leaks.
Added the test:server-app-station-routing script to package.json and wired it into the npm test execution chain.

Risk Assessment

✅ Low: Test-only change adding an end-to-end Server App multi-station KOT routing integration test and wiring it into package.json without touching production code.

Testing

Executed npm run test:server-app-station-routing, npm run test:script-coverage, npm run test:issue-134-routing, npm run test:issue-134-mgmt, and npm run test:server-app-maintenance-handoff, and stood up an isolated live instance of the Server App, Main API, KDS Server, and three local TCP raw-printer socket listeners to drive all five multi-station KOT routing scenarios end-to-end without route or socket stubs. Captured the decoded ESC/POS thermal tickets and test outputs as evidence artifacts; no visual screenshot artifact was captured because this change adds a backend/transport integration test with no UI/HTML/CSS changes, and all scenarios passed.

Live validation: ✅ go - 5 of 5 scenarios driven live against the product

Scenario	Result	Live	Evidence
Waiter logs into the Server App, creates a multi-category dine-in order (Grill, Bar, and unmapped Desserts), and posts /api/printers/print-kot with { orderId, items } and no stationName; the Server Ap…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario1_sendOrderWithItems) and `npm run test:server-app-station-routing`
Waiter triggers Server App POST /api/printers/print-kot with { orderId } only (omitting items and stationName); persisted pending order items are loaded from SQLite and routed into 3 separate ESC/POS…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario2_orderIdOnly) and `npm run test:server-app-station-routing`
Waiter appends a Bar item and an unmapped Dessert item to an existing order via Server App POST /api/orders/:id/items and calls POST /api/printers/print-kot with only the newly added items delta; only…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario3_appendItemsDelta) and `npm run test:server-app-station-routing`
When the Bar kitchen station is deactivated (is_active = 0), posting /api/printers/print-kot through the Server App routes Grill items to the Grill Station Printer, sends zero dispatches to the inacti…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario4_inactiveStationFallback) and `npm run test:server-app-station-routing`
Adversarial bypass check: passing an explicit stationName ("Kitchen") to POST /api/printers/print-kot bypasses per-station routing into a single combined ticket on the Default Kitchen Printer, and the…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario5_explicitStationBypass) and `npm run test:server-app-station-routing`

Evidence: Live Server App multi-station TCP ESC/POS KOT dispatch transcript

Station: Grill (335 bytes) -> 2x Ribeye Steak, 1x Charbroiled Burger Station: Bar (303 bytes) -> 3x Classic Mojito Station: Kitchen (310 bytes) -> 1x Basque Cheesecake

{
  "serverAppBaseUrl": "http://127.0.0.1:50484",
  "tcpPrinters": {
    "kitchenPort": 50491,
    "grillPort": 50492,
    "barPort": 50493
  },
  "scenarios": {
    "scenario1_sendOrderWithItems": {
      "httpStatus": 200,
      "response": {
        "success": true,
        "warnings": []
      },
      "grillDispatches": [
        {
          "stationLabel": "Grill Station Printer",
          "byteLength": 335,
          "text": "KITCHEN ORDER TICKET\n\nStation: Grill\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n2x  Ribeye Steak\n1x  Charbroiled Burger\n\n=========================================="
        }
      ],
      "barDispatches": [
        {
          "stationLabel": "Bar Station Printer",
          "byteLength": 303,
          "text": "KITCHEN ORDER TICKET\n\nStation: Bar\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n3x  Classic Mojito\n\n=========================================="
        }
      ],
      "kitchenDispatches": [
        {
          "stationLabel": "Main Kitchen Printer (Default)",
          "byteLength": 310,
          "text": "KITCHEN ORDER TICKET\n\nStation: Kitchen\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n1x  Basque Cheesecake\n\n=========================================="
        }
      ]
    },
    "scenario2_orderIdOnly": {
      "httpStatus": 200,
      "response": {
        "success": true,
        "warnings": []
      },
      "grillDispatches": [
        {
          "stationLabel": "Grill Station Printer",
          "byteLength": 335,
          "text": "KITCHEN ORDER TICKET\n\nStation: Grill\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n2x  Ribeye Steak\n1x  Charbroiled Burger\n\n=========================================="
        }
      ],
      "barDispatches": [
        {
          "stationLabel": "Bar Station Printer",
          "byteLength": 303,
          "text": "KITCHEN ORDER TICKET\n\nStation: Bar\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n3x  Classic Mojito\n\n=========================================="
        }
      ],
      "kitchenDispatches": [
        {
          "stationLabel": "Main Kitchen Printer (Default)",
          "byteLength": 310,
          "text": "KITCHEN ORDER TICKET\n\nStation: Kitchen\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n1x  Basque Cheesecake\n\n=========================================="
        }
      ]
    },
    "scenario3_appendItemsDelta": {
      "httpStatus": 200,
      "response": {
        "success": true,
        "warnings": []
      },
      "grillDispatches": [],
      "barDispatches": [
        {
          "stationLabel": "Bar Station Printer",
          "byteLength": 303,
          "text": "KITCHEN ORDER TICKET\n\nStation: Bar\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n1x  Classic Mojito\n\n=========================================="
        }
      ],
      "kitchenDispatches": [
        {
          "stationLabel": "Main Kitchen Printer (Default)",
          "byteLength": 310,
          "text": "KITCHEN ORDER TICKET\n\nStation: Kitchen\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n2x  Basque Cheesecake\n\n=========================================="
        }
      ]
    },
    "scenario4_inactiveStationFallback": {
      "httpStatus": 200,
      "response": {
        "success": true,
        "warnings": []
      },
      "grillDispatches": [
        {
          "stationLabel": "Grill Station Printer",
          "byteLength": 335,
          "text": "KITCHEN ORDER TICKET\n\nStation: Grill\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n2x  Ribeye Steak\n1x  Charbroiled Burger\n\n=========================================="
        }
      ],
      "barDispatches": [],
      "kitchenDispatches": [
        {
          "stationLabel": "Main Kitchen Printer (Default)",
          "byteLength": 338,
          "text": "KITCHEN ORDER TICKET\n\nStation: Kitchen\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n3x  Classic Mojito\n1x  Basque Cheesecake\n\n=========================================="
        }
      ]
    },
    "scenario5_explicitStationBypass": {
      "httpStatus": 200,
      "response": {
        "success": true,
        "warnings": []
      },
      "grillDispatches": [],
      "barDispatches": [],
      "kitchenDispatches": [
        {
          "stationLabel": "Main Kitchen Printer (Default)",
          "byteLength": 396,
          "text": "KITCHEN ORDER TICKET\n\nStation: Kitchen\nOrder #ORD-20261028-0001\nTable: T1\nType: Dine in\nTime: 4:57:50 PM\n==========================================\n\n2x  Ribeye Steak\n1x  Charbroiled Burger\n3x  Classic Mojito\n1x  Basque Cheesecake\n\n=========================================="
        }
      ]
    }
  }
}

Evidence: Server App station routing integration test and script-coverage output

✓ Waiter App print-kot (with items, no stationName) routed to Grill, Bar, and fallback Kitchen printers ✓ Waiter App print-kot (orderId only, no stationName) routed DB items to Grill, Bar, and fallback Kitchen printers ✓ Waiter App append-items print-kot routed only touched stations (Bar + fallback Kitchen) ✓ Inactive station (stn-bar) items fell back to Default Kitchen printer while Grill routed normally ✓ Routing assertion rejects bypassed single-ticket and cross-station dispatches ALL PASSED Test script coverage OK: 267 reachable, 8 explicitly excluded. Test file coverage OK: 327 run by the default suite, 1 excluded with a stated reason.


> flo-desktop@3.13.14 test:server-app-station-routing
> node tests/run-electron-node-test.cjs tests/server-app-station-routing.test.ts

Integration Test: Server App end-to-end multi-station KOT routing (#1348)
==========================================================================
[DB] Opening database at: /var/folders/y_/1ltcxtwj0zd_w1dg9jv4jl580000gn/T/flo-server-app-station-routing-ik2yxP/flo.db
[DB] Schema: v0 → v118
[DB] Triggering auto-backup before migrating v0 → v118...
[DB] Auto-backup before migrating v0 → v118 created at /var/folders/y_/1ltcxtwj0zd_w1dg9jv4jl580000gn/T/flo-server-app-station-routing-ik2yxP/backups/flo-backup-2026-10-28T20-58-10-744Z-pre-v0-to-v118.db
[DB] Install defaults loaded; first-run setup pending
[MIGRATION v23] normalized: 0, unparseable: 0
[MIGRATION v23] merged 0 duplicate customer(s)
[MIGRATION v23] verification: 0 customers, 0 still non-E.164
[MIGRATION v24] normalized: 0, unparseable: 0
[MIGRATION v25] backfilled addons for 0 order items (0 unparseable, skipped)
[MIGRATION v30] backfilled 0 order_item(s) still missing a normalized addons snapshot
[MIGRATION v30] Dropped order_items.addons — order_item_addons is now the only place selected addons live.
[MIGRATION v73] normalized 0 merchant template payload(s); 0 already canonical or left untouched
[DB] integrity_check: ok
[DB] foreign_key_check: clean
[Server] Frontend build not found. Run `npm run build:frontend` first.
[Server] HTTP server running on http://localhost:50554
[KDS] WebSocket server setup complete
[Server] KDS WebSocket running on ws://localhost:50554/kds
[WhatsApp] {"event":"startup_init","enabled":false,"hasCredentials":false,"connectedPhone":null}
[KDS Server] Static build not found. Run `npm run build:frontend` first.
[KDS Server] HTTP server running on http://localhost:50555
[KDS] WebSocket server setup complete
[KDS Server] WebSocket running on ws://localhost:50555/kds
[Server App] Static build not found. Run `npm run build:frontend` first.
[Server App] HTTP server running on http://localhost:50556
[Auth] Generated new JWT secret for this install
[Printer] printKOT called, items count: 2 useUnicode: false station: Grill
[Printer] Using printer: Grill Station Printer network
[Printer] KOT data length: 335 bytes
[Printer] printKOT called, items count: 1 useUnicode: false station: Bar
[Printer] Using printer: Bar Station Printer network
[Printer] KOT data length: 303 bytes
[Printer] printKOT called, items count: 1 useUnicode: false station: Kitchen
[Printer] Using printer: Main Kitchen Printer network
[Printer] KOT data length: 310 bytes
  ✓ Waiter App print-kot (with items, no stationName) routed to Grill, Bar, and fallback Kitchen printers
[Printer] printKOT called, items count: 2 useUnicode: false station: Grill
[Printer] Using printer: Grill Station Printer network
[Printer] KOT data length: 335 bytes
[Printer] printKOT called, items count: 1 useUnicode: false station: Bar
[Printer] Using printer: Bar Station Printer network
[Printer] KOT data length: 303 bytes
[Printer] printKOT called, items count: 1 useUnicode: false station: Kitchen
[Printer] Using printer: Main Kitchen Printer network
[Printer] KOT data length: 310 bytes
  ✓ Waiter App print-kot (orderId only, no stationName) routed DB items to Grill, Bar, and fallback Kitchen printers
[Printer] printKOT called, items count: 1 useUnicode: false station: Bar
[Printer] Using printer: Bar Station Printer network
[Printer] KOT data length: 303 bytes
[Printer] printKOT called, items count: 1 useUnicode: false station: Kitchen
[Printer] Using printer: Main Kitchen Printer network
[Printer] KOT data length: 310 bytes
  ✓ Waiter App append-items print-kot routed only touched stations (Bar + fallback Kitchen)
[Printer] printKOT called, items count: 2 useUnicode: false station: Grill
[Printer] Using printer: Grill Station Printer network
[Printer] KOT data length: 335 bytes
[Printer] printKOT called, items count: 2 useUnicode: false station: Kitchen
[Printer] Using printer: Main Kitchen Printer network
[Printer] KOT data length: 338 bytes
  ✓ Inactive station (stn-bar) items fell back to Default Kitchen printer while Grill routed normally
[Printer] printKOT called, items count: 4 useUnicode: false station: Kitchen
[Printer] Using printer: Main Kitchen Printer network
[Printer] KOT data length: 396 bytes
  ✓ Routing assertion rejects bypassed single-ticket and cross-station dispatches
[Server App] HTTP server stopped
[KDS Server] HTTP/WebSocket server stopped
[Server] HTTP/WebSocket server stopped
[DB] Database closed
ALL PASSED

> flo-desktop@3.13.14 test:script-coverage
> node scripts/ci/validate-test-script-coverage.cjs && node tests/test-script-coverage.test.cjs && ts-node --transpile-only -P tests/tsconfig.json tests/test-harness-assertions.test.ts

Test script coverage OK: 267 reachable, 8 explicitly excluded.
Test file coverage OK: 327 run by the default suite, 1 excluded with a stated reason.
Test-script command parsing verified.
Test harness assertion contract
  ✗ deliberate counting failure
  ✗ deliberate counting failure — expected 2, got 1
  ✗ deliberate counting failure — "abc" does not contain "z"
  ✗ deliberate counting failure — expected > 2, got 1
  ✗ deliberate throwing failure
  ✗ deliberate throwing failure — expected 2, got 1
  ✗ deliberate throwing failure — "abc" does not contain "z"
  ✗ deliberate throwing failure — expected > 2, got 1
  ✓ harness contract verified

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

Live validation: ✅ go - 5 of 5 scenarios driven live against the product

Scenario	Result	Live	Evidence
Waiter logs into the Server App, creates a multi-category dine-in order (Grill, Bar, and unmapped Desserts), and posts /api/printers/print-kot with { orderId, items } and no stationName; the Server Ap…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario1_sendOrderWithItems) and `npm run test:server-app-station-routing`
Waiter triggers Server App POST /api/printers/print-kot with { orderId } only (omitting items and stationName); persisted pending order items are loaded from SQLite and routed into 3 separate ESC/POS…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario2_orderIdOnly) and `npm run test:server-app-station-routing`
Waiter appends a Bar item and an unmapped Dessert item to an existing order via Server App POST /api/orders/:id/items and calls POST /api/printers/print-kot with only the newly added items delta; only…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario3_appendItemsDelta) and `npm run test:server-app-station-routing`
When the Bar kitchen station is deactivated (is_active = 0), posting /api/printers/print-kot through the Server App routes Grill items to the Grill Station Printer, sends zero dispatches to the inacti…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario4_inactiveStationFallback) and `npm run test:server-app-station-routing`
Adversarial bypass check: passing an explicit stationName ("Kitchen") to POST /api/printers/print-kot bypasses per-station routing into a single combined ticket on the Default Kitchen Printer, and the…	✅ pass	live	~/.no-mistakes/evidence/01M624FYP5RKN5ZT9N6Y4Y0JE5/server-app-station-routing-live-transcript.json (scenario5_explicitStationBypass) and `npm run test:server-app-station-routing`

npm run test:server-app-station-routing
npm run test:script-coverage
npm run test:issue-134-routing
npm run test:issue-134-mgmt
npm run test:server-app-maintenance-handoff
Live end-to-end Server App + Main API + KDS Server + 3 TCP raw-printer listeners harness (node tests/run-electron-node-test.cjs -e ...)

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

coderabbitai · 2026-10-27T21:48:33Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

Source mode: Auto
Repository: FreeOpenSourcePOS/FloCafe
Branch: fm/flocafe-1348-server-app-station-routing
File: .coderabbit.yaml
Commit: 1679b10
Layers: Repository YAML
Review profile: CHILL
Plan: Advanced
Run ID: 97a20f63-dce8-43f7-9136-33d52ebdc1e7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

qodo-code-review · 2026-10-27T21:48:59Z

PR Summary by Qodo

Test Server App KOT routing across kitchen stations

🧪 Tests ⚙️ Configuration changes 🕐 20-40 Minutes

AI Description

• Add an HTTP integration test for waiter orders routed through the Server App to station printers.
• Verify Grill and Bar receive separate KOTs while unmapped desserts reach the default Kitchen
 printer.
• Cover initial and appended items, and run the test in the standard suite.

Diagram

sequenceDiagram
    actor Test as Waiter test
    participant App as Server App
    participant API as Main API
    participant DB as Test database
    participant Route as Station routing
    participant Thermal as Thermal printing
    participant Socket as Socket stub
    Test->>App: Create order and request KOT
    App->>API: Forward authenticated requests
    API->>DB: Load order and printer mappings
    API->>Route: Group pending items
    Route-->>API: Grill, Bar, Kitchen groups
    loop Each nonempty group
        API->>Thermal: Print station KOT
        Thermal->>Socket: Send ESC/POS bytes
    end
    Socket-->>Test: Recorded dispatches

High-Level Assessment

The HTTP integration test is well matched to the missing coverage: it exercises forwarding and routing together while stubbing only physical printer connections. A routing unit test would miss forwarding regressions, while browser-driven testing would add setup and UI dependencies without improving verification of printer dispatch.

Files changed (2) +556 / -1

Tests (2) +556 / -1

package.jsonRegister station-routing integration test +2/-1

Register station-routing integration test

• Adds a dedicated Electron-node test command and includes it in the standard test script, making the new test discoverable by script-coverage validation.

package.json

server-app-station-routing.test.tsVerify Server App KOT dispatch to mapped and fallback printers +554/-0

Verify Server App KOT dispatch to mapped and fallback printers

• Creates a waiter order through the Server App and checks that Grill, Bar, and unmapped Dessert items print on separate station-specific KOTs. Also covers order-ID-only printing, appended-item printing, and assertions that reject single-ticket routing or cross-station item leakage; physical printer sockets are stubbed while HTTP forwarding remains live.

tests/server-app-station-routing.test.ts

qodo-code-review · 2026-10-27T21:51:19Z

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. ~~Appended tickets can use the wrong port~~ ✓ Resolved

Description

The append-flow assertions identify the Bar and Kitchen dispatches by IP address but never check
their recorded ports. If an appended ticket is sent to the right IP on the wrong port, this scenario
still passes even though the ticket has not reached its configured printer endpoint.

Code

tests/server-app-station-routing.test.ts[472]
+    const appendedBar = recordedDispatches.find((d) => d.ip === BAR_STATION_PRINTER.ip);

Relevance

●●● Strong
Test assertion misses configured port; accepted precedents favor strengthening tests against false
positives.
PR-#1261
PR-#1119

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The socket stub records each dispatch's actual port, and the printer fixtures define expected ports.
Unlike the initial-order assertions, the append-flow lookup uses only IP, so its content checks
cannot detect a wrong-port dispatch.
tests/server-app-station-routing.test.ts[58-84]
tests/server-app-station-routing.test.ts[204-218]
tests/server-app-station-routing.test.ts[467-479]
tests/server-app-station-routing.test.ts[141-169]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The append-flow test accepts dispatches to the expected IP even when they use the wrong printer port.
## Fix Focus Areas
- tests/server-app-station-routing.test.ts[467-479]
## Recommended Fix
Match both IP and configured port for the appended Bar and Kitchen tickets, and assert that neither printer receives an extra dispatch.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Context sources

⚠️ Tickets: not configured — No jira, linear integration is connected for the linked tickets

✅ Compliance rules (platform): 5 rules

✅ Cross-repo context — repo relationships

Review mode: Auto: ⚖️ Balanced: Substantial integration-test logic and lifecycle mocking warrant a careful single-pass review.

Tip of the day

💡 Did you know, you can turn on the rule miner and Qodo learns your standards from review history

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Fixes #1348

khaira777 requested review from carvalab and itsbkm as code owners October 27, 2026 21:48

qodo-code-review Bot reviewed Oct 27, 2026

View reviewed changes

Comment thread tests/server-app-station-routing.test.ts Outdated

khaira777 changed the title ~~test: verify end-to-end multi-station KOT routing from the Server App~~ test(server-app): e2e multi-station KOT routing Oct 27, 2026

khaira777 changed the title ~~test(server-app): e2e multi-station KOT routing~~ test(server-app): end-to-end multi-station KOT routing Oct 28, 2026

khaira777 changed the title ~~test(server-app): end-to-end multi-station KOT routing~~ test(server-app): e2e multi-station KOT routing Oct 28, 2026

khaira777 added 3 commits October 28, 2026 16:51

test(server-app): e2e multi-station KOT routing

a860e93

Fixes #1348

test(server-app): assert port and count on append KOT

14364e9

test(server-app): verify inactive station KOT fallback

1679b10

khaira777 force-pushed the fm/flocafe-1348-server-app-station-routing branch from 8529d8e to 1679b10 Compare October 28, 2026 21:00

khaira777 changed the title ~~test(server-app): e2e multi-station KOT routing~~ test(server-app): end-to-end multi-station KOT routing from the waiter app Oct 28, 2026

khaira777 changed the title ~~test(server-app): end-to-end multi-station KOT routing from the waiter app~~ test(server-app): e2e multi-station KOT routing Oct 28, 2026

khaira777 merged commit 306bf32 into main Oct 28, 2026
23 checks passed

khaira777 deleted the fm/flocafe-1348-server-app-station-routing branch October 28, 2026 21:08

Navigation Menu

Repository navigation

test(server-app): e2e multi-station KOT routing - #1388

test(server-app): e2e multi-station KOT routing#1388
khaira777 merged 3 commits into
mainfrom
fm/flocafe-1348-server-app-station-routing

khaira777 commented Oct 27, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Oct 27, 2026 •

edited

Loading

Review skipped

Uh oh!

qodo-code-review Bot commented Oct 27, 2026

Uh oh!

qodo-code-review Bot commented Oct 27, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

khaira777 commented Oct 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Intent

What Changed

Risk Assessment

Testing

Pipeline

Uh oh!

coderabbitai Bot commented Oct 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

qodo-code-review Bot commented Oct 27, 2026

PR Summary by Qodo

Uh oh!

qodo-code-review Bot commented Oct 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Uh oh!

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

khaira777 commented Oct 27, 2026 •

edited

Loading

coderabbitai Bot commented Oct 27, 2026 •

edited

Loading

qodo-code-review Bot commented Oct 27, 2026 •

edited

Loading