Printer unresponsive status E2E

This page documents the real-app end-to-end check for the printer unresponsive connection status.

The screenshots below are captured from the actual Expo web app (frontend/App.js through Main, UserLayout, UserPrinterStatusConnection, and NavBarMenuSettingsModalPrintersItem). The E2E script simulates the backend responses that a dmesg-backed poller failure would produce:

{
  "connectionStatus": "unresponsive",
  "connectionDiagnostic": "[73476.224266] usb 3-2: device descriptor read/64, error -71\n[73492.234561] usb usb2-port4: attempt power cycle"
}

Only the backend API inputs are mocked; the rendered UI is the real application.

How to reproduce

Start the development stack or otherwise serve the frontend web app on http://127.0.0.1:8081:

./run.sh -e dev --no-build

Then run the real-app Playwright check:

python3 scripts/e2e_printer_unresponsive_status.py

The script saves screenshots into docs/assets/printer-unresponsive-status/.

E2E evidence

The test asserts:

the active printer page renders unresponsive from /user/printer/selected/status;
the main status question-mark diagnostic modal includes the internal dmesg error snippet;
the settings printer card badge renders unresponsive;
clicking the settings badge opens a diagnostic modal with the same filtered kernel context;
clicking Edit on the printer shows the detailed diagnostic box in the details tab.