Test Palot Desktop

Test Palot Desktop

Use this skill for the native Electron client. A renderer-only Vite page does not prove the preload, IPC, or OpenCode connection.

Use repository-root ../../../docs/agent-development.md for verification selection, launch, renderer attachment, artifact paths, and cleanup. Read ../../../docs/desktop-testing.md when authoring scenarios or resolving test-architecture questions.

Choose The Path

• Agent worktree: run the smallest matching bun run test:e2e -- <scenario>. The harness is hidden, credential-free, isolated, and self-cleaning.
• Deterministic visual review: add --visible.
• Renderer recording: add --video (requires ffmpeg, implies --visible --keep). Captures the explicit Electron renderer, not desktop chrome/audio. Retains video.mp4 and video.json; recording adds overhead and is not compositor/FPS evidence. Inspect representative frames before presenting the private recording.
• Agent inspection: add --inspect, then run the exact agent-browser connect '<renderer-websocket>' command printed by the harness. Use the renderer target rather than browser-level CDP because Electron cannot create a new target. Stop the retained command with Ctrl-C.
• Real-provider behavior or requested live inspection: use the live workflow below. It connects to real user data.

List deterministic scenarios with bun run test:e2e:list. Failures retain available evidence under the primary checkout's .local/desktop-e2e/; report the absolute run path and which artifacts exist. Early setup failures may have no screenshot.

Complete only the selected path below. Running an isolated scenario does not require live inspection or a full shell smoke pass.

Deterministic E2E

Use the scenario result as evidence for the behavior it asserts. Scripted data in an isolated OpenCode service is valid integration evidence; it does not prove live provider behavior. Inspect failures before widening the test scope.

Report the scenario command, result, unresolved failures, and retained artifact path when present. A passing nonvisual scenario needs neither real user data nor screenshots. For visual QA, also inspect the affected state and save a screenshot; use before/after images when both states are available.

Live inspection

Use this path only for real-provider behavior or requested live inspection. Follow the live development and renderer attachment commands in ../../../docs/agent-development.md. Reuse a healthy development terminal owned by this task when possible. Keep the terminal or spawned process identifier for cleanup.

Use bun run dev for hidden integration, dev:visible for visual inspection, or dev:focus when focus behavior matters. Use the development launcher rather than signed packaging. An unsigned package check requires the user's request.

Live Palot connects to the user's shared OpenCode 2 service. Start with read-only navigation. Create sessions, submit prompts, interrupt work, or answer requests only when the test scope authorizes those changes, and use a disposable test session.

Private evidence

Run from the repository root. Resolve the primary checkout and create one QA directory:

primary_checkout="$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")"
qa_stamp="$(date +%Y%m%d-%H%M%S)"
qa_dir="$primary_checkout/.local/desktop-qa/$qa_stamp"
mkdir -p "$qa_dir"
printf '%s\n' "$qa_dir"

Keep screenshots, copied logs, and notes in this directory. Do not put project names, session titles, prompt text, credentials, or tokens in artifact names. Inspect each screenshot for sensitive data before you show or attach it.