dev-test-electron

Automate Electron app testing and debugging via Chrome DevTools Protocol.

19|5|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/edwinhu/workflows --skill dev-test-electron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-test-electron
Source: https://github.com/edwinhu/workflows/tree/main/lib/skills/dev-test-electron
Command: npx skills add https://github.com/edwinhu/workflows --skill dev-test-electron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a robust framework for end-to-end testing and debugging of Electron desktop applications, ensuring they function correctly across different user interactions and environments.

Core Features & Use Cases

  • Chrome DevTools Protocol (CDP) Automation: Connects to Electron's renderer and main processes for deep inspection and control.
  • Full 6-Gate TDD Enforcement: Integrates with a strict testing methodology, ensuring code is built, launched, verified, and logged before E2E tests run.
  • Use Case: Automatically test a VS Code extension by simulating user input, verifying UI changes, and checking console logs via CDP, ensuring the extension behaves as expected in a real Electron environment.

Quick Start

Execute the example script /examples/basic-test.sh to run a full E2E test on your Electron application.

Frequently Asked Questions about dev-test-electron

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

FAQPage Schema
How do I automate end-to-end testing for an Electron desktop application?

Automate Electron end-to-end testing by connecting to the renderer and main processes via the Chrome DevTools Protocol (CDP), simulating user input, verifying UI changes, and analyzing console logs to validate application behavior.

Can I debug both the main and renderer processes in Electron using CDP?

Yes, CDP enables deep inspection and control for debugging both the Electron main and renderer processes, allowing direct interaction with application internals during automated test execution.

What is a 6-gate TDD workflow for Electron testing?

A 6-gate TDD workflow enforces a strict testing methodology ensuring the application is built, launched, verified, and logged before end-to-end tests execute, validating behavior through CDP commands.

Does this CDP testing approach work for testing VS Code extensions?

Yes, you can automatically test a VS Code extension by simulating user input, verifying UI changes, and checking console logs via CDP to ensure expected behavior in a real Electron environment.

How do I get started with running an E2E test on my Electron app?

Execute the example script `/examples/basic-test.sh` to run a full end-to-end test cycle on your Electron application using CDP automation and the enforced 6-gate TDD workflow.

Why should I use CDP over other automation tools for Electron testing?

Using CDP facilitates deep inspection and control of both main and renderer processes, enabling thorough log analysis and UI verification that standard automation frameworks may not expose directly.