🔍 Multi-Device Docs Testing Report - 2026-07-17

[github-actions]

Test Summary

• Triggered by: @pelikhan
• Workflow run: §29559253225
• Devices targeted: 10
• Devices fully browser-tested: 0
• Test date: 2026-07-17

Results Overview

• 🟢 Passed: 0
• 🟡 Warnings: 1
• 🔴 Critical: 2

Critical Issues

1. Playwright-based multi-device validation could not run in this environment. playwright-cli failed to launch Chrome in headless mode because the Chrome sandbox helper is not configured correctly (chrome-sandbox SUID configuration error). This blocked viewport rendering, interaction testing, screenshots, and accessibility checks across all requested devices.
2. Server availability precondition was not met from the workflow setup. The initial required check to (localhost/redacted) failed. I had to manually start npm run previewindocs/` to make the site reachable, which indicates the pre-agent preview bootstrapping was not actually available at test start.

View All Warnings

• Static HTML inspection of `(localhost/redacted) suggests the homepage shell is present (header, nav, main, footer, search button, dialog markup, tablet hamburger markup, mermaid block, slide-preview canvas). However, because runtime browser execution was blocked, this is only a partial confidence check and not a substitute for responsive rendering validation.
• A direct HTML fetch did not expose an explicit skip-link anchor in the initial markup (href="#_top" was not present in server HTML). There is an inline enhancement script that adds id="starlight__main" / tabindex="-1" to <main>, but this still needs real browser verification to confirm keyboard accessibility behavior.

View Detailed Test Results by Device

Mobile Devices

• iPhone 12 (390x844): blocked by Playwright/Chrome launch failure before navigation
• iPhone 12 Pro Max (428x926): blocked by Playwright/Chrome launch failure before navigation
• Pixel 5 (393x851): blocked by Playwright/Chrome launch failure before navigation
• Galaxy S21 (360x800): blocked by Playwright/Chrome launch failure before navigation

Tablet Devices

• iPad (768x1024): blocked by Playwright/Chrome launch failure before navigation
• iPad Pro 11 (834x1194): blocked by Playwright/Chrome launch failure before navigation
• iPad Pro 12.9 (1024x1366): blocked by Playwright/Chrome launch failure before navigation

Desktop Devices

• HD (1366x768): blocked by Playwright/Chrome launch failure before navigation
• FHD (1920x1080): blocked by Playwright/Chrome launch failure before navigation
• 4K (2560x1440): blocked by Playwright/Chrome launch failure before navigation

Partial Static Verification Performed

• Confirmed docs preview responds with HTTP 200 after manually starting astro preview.
• Confirmed homepage HTML contains major structural elements: <header>, <nav>, <main>, <footer>.
• Confirmed presence of search trigger markup (aria-label="Search"), search dialog, CTA links, tablet navigation toggle markup, mermaid content, and workflow slide canvas.

Accessibility Findings

• Blocked: No browser-driven accessibility audit could be completed due to the Playwright/Chrome sandbox launch failure.
• Potential concern: Skip-link behavior and keyboard navigation enhancements appear to rely partly on client-side scripts; these were not verifiable without a functioning browser session.

Recommendations

1. Fix the CI Playwright browser runtime so playwright-cli can launch successfully in this environment. The observed blocker is a Chrome sandbox helper configuration failure.
2. Ensure the docs preview server is confirmed alive before handing control to the agent; the workflow’s documented pre-agent startup assumption did not hold at runtime.
3. Re-run the multi-device pass after browser launch is fixed, including screenshots, navigation interactions, and accessibility checks across all 10 viewports.

References:

• §29559253225

Generated by 📝 Multi-Device Docs Tester · 14.8 AIC · ⌖ 9.7 AIC · ⊞ 5.2K · ◷

• expires on Jul 18, 2026, 10:18 PM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 1.2 AIC · ⌖ 10.8 AIC · ⊞ 7.1K · ◷