electron-test-e2e
Skill1 starsChanged 4 months agoMITView on GitHub
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.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- electron-debugSkill
- electron-implementationSkill
- electron-ipc-securitySkill
- electron-releaseSkill
- electron-reviewSkill
- github-deliverySkill
- handoffSkill
- handonSkill
- making-thingsSkill
- mts-moreSkill
- mts-oneSkill
- mts-splitSkill
- product-prdSkill
- solution-architectureSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the sidecar contract, matching track/task, current implementation, references/testing-standard.md, and references/test-strategy.md.
- Distinctive: line 17
Use condition-based waits, deterministic system mocks, and clean resource teardown.
- Distinctive: line 22
Create/advance integration tasks only after their declared frontend and backend deliverables are complete.
- Distinctive: line 25
Do not replace a product bug with a permissive test, fixed sleep, swallowed error, or deleted assertion.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.