skills.rest
laststance
laststanceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

qa-electron

Automate Electron app QA via CDP and Playwright CLI across platforms.

1|1|Updated Feb 13, 2026
Search Tags:#automation#qa#playwright#electron#cdp#matrix#os-integration
One-click install
npx skills add https://github.com/laststance/skills --skill qa-electron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-electron
Source: https://github.com/laststance/skills/tree/main/skills/qa-electron
Command: npx skills add https://github.com/laststance/skills --skill qa-electron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Electron-based desktop apps often ship with complex UI and native OS integrations that require end-to-end QA across multiple windows, surfaces, and platforms. This Skill provides a structured, phase-based approach to test Electron apps using CDP-driven rendering, logs, and OS automation to ensure UI fidelity and reliability.

Core Features & Use Cases

  • Phase-driven QA workflow covering surface mapping, test-matrix generation, multi-window coverage, accessibility, and security checks.
  • Cross-platform, CDP-enabled renderer automation using playwright-cli, with native OS driving via osascript (macOS) or alternative tools.
  • Comprehensive report and triage output templates to guide debugging and remediation.

Quick Start

Launch the Electron app with a remote debugging port, attach playwright-cli to the port, and follow Phase 0 through Phase 12 to complete a QA run.

Frequently Asked Questions about qa-electron

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate QA testing for an Electron desktop app?▼

Automate QA for Electron apps by driving the Chrome DevTools Protocol (CDP) to exercise renderers, logs, and native OS surfaces. This approach uses a phase-based workflow to ensure UI fidelity and reliability across macOS, Windows, and Linux.

What is the best way to test multi-window coverage in Electron apps?▼

Multi-window coverage in Electron apps is tested using CDP-enabled renderer automation via Playwright CLI. The structured workflow covers surface mapping, test-matrix generation, and multi-window validation to comprehensively exercise complex UI states.

Does Electron QA automation require host OS accessibility permissions?▼

Yes, Electron QA automation requires host OS accessibility permissions to drive native OS surfaces. The workflow uses osascript on macOS or alternative tools to interact with native integrations alongside CDP-driven renderer testing.

How do I start Playwright CLI automation with a remote debugging port in Electron?▼

Launch the Electron app with a remote debugging port, attach Playwright CLI to that port, and follow the phase-based workflow from Phase 0 through Phase 12. This systematically completes the QA run including accessibility and security checks.

Can I generate a test matrix for cross-platform Electron apps on Windows and Linux?▼

Yes, you can generate a test matrix for cross-platform Electron apps on Windows and Linux. The workflow applies phase-driven test-matrix generation to ensure comprehensive surface mapping and UI coverage across different operating systems.

Related Skills

Explore More Software Engineering Skills→
vercel-labsvercel-labs
40.3k

electron

Automate Electron desktop app interactions via Chrome DevTools Protocol.

Official
Advanced
OmerFarukOrucOmerFarukOruc
2

investigate

Identify and resolve software issue root causes through a structured investigation workflow.

Community
Advanced
andershi666andershi666
1

local-testing

Automate end-to-end macOS app and bot testing via agent-browser and osascript.

Community
Advanced
cloudofgeorgecloudofgeorge

macos-accessibility

Automate macOS applications via AXUIElement APIs with TCC permission validation and security controls.

Community
Advanced