Electron test e2e
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.From its SKILL.md
npx -y skills add SuShuheng/making-things --skill electron-test-e2eAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
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, andreferences/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.