| name | electron-test-e2e |
| description | Use when an Electron work item needs test planning, unit or IPC coverage, preload contract tests, Playwright Electron E2E, multi-window checks, or packaged smoke evidence. Do not use to invent passing results, bypass a failing gate, or authorize release. |
Electron Test E2E
Build evidence from cheap deterministic layers to platform-specific packaged tests.
- Read the sidecar contract, matching track/task, current implementation,
references/testing-standard.md, and references/test-strategy.md.
- Map each task requirement/risk to a test layer and expected observation.
Frontend tasks cover renderer behavior; backend tasks cover service, IPC
authorization/validation, and preload shape; integration tasks cover
cross-track Electron flows and E2E.
- Capture the intended failing test/reproducer before the behavior change.
Use condition-based waits, deterministic system mocks, and clean resource
teardown.
- Record exact commands, UTC time, OS/architecture, exit code, counts, and
safe artifact locations in the selected task's Evidence. Label unexercised
platforms, architectures, signing, and packaged modes
NOT RUN.
- Create/advance integration tasks only after their declared frontend and
backend deliverables are complete.
Do not replace a product bug with a permissive test, fixed sleep, swallowed error, or deleted assertion.
