ui-test-electron

Create and run Playwright End-to-End tests for Electron desktop applications.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/helm-ade-toolkit --skill ui-test-electron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-test-electron
Source: https://github.com/mdmagnuson-creator/helm-ade-toolkit/tree/main/skills/ui-test-electron
Command: npx skills add https://github.com/mdmagnuson-creator/helm-ade-toolkit --skill ui-test-electron

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides comprehensive guidance and patterns for writing robust End-to-End (E2E) tests for desktop applications built with Electron, ensuring their quality and stability.

Core Features & Use Cases

  • Playwright Integration: Leverages Playwright for powerful browser automation capabilities tailored for Electron.
  • Launch Configuration: Guides users through resolving the correct launch target and configuration based on project.json settings.
  • Zombie Process Management: Offers critical solutions for cleaning up orphaned Electron processes to prevent test failures.
  • Main & Renderer Process Testing: Provides patterns for interacting with both the main and renderer processes of an Electron app.
  • Use Case: You need to write automated E2E tests for your company's desktop application built with Electron, ensuring that UI interactions, inter-process communication, and native dialogs function correctly across different launch configurations.

Quick Start

Use the ui-test-electron skill to set up Playwright E2E tests for your Electron application, ensuring zombie processes are cleaned up before each run.

Frequently Asked Questions about ui-test-electron

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

FAQPage Schema
How do I write End-to-End tests for an Electron desktop app?

You can write end-to-end tests for an Electron desktop app by leveraging Playwright integration to automate UI interactions, inter-process communication, and native dialog handling. This approach covers testing both renderer and main processes.

Why does my Electron test suite fail due to zombie processes?

Electron test suites often fail due to orphaned zombie processes left from previous runs. You can resolve this by implementing a global setup script that cleans up these orphaned Electron processes before each test execution to ensure stability.

Can I test Electron applications using Playwright with different launch configurations?

Yes, Playwright supports testing Electron apps with different launch configurations. It resolves the correct launch target and settings based on your project configuration, supporting both development environments and installed application targets.

What is the best way to handle native dialogs in Electron E2E testing?

The best way to handle native dialogs in Electron E2E testing is by using Playwright patterns designed specifically for desktop applications. These patterns allow you to interact with and validate native dialog behaviors during automated test execution.

How do I test the main process of an Electron application?

You test the main process of an Electron application by using specialized testing patterns that interact directly with it. This ensures that background logic and inter-process communication function correctly alongside renderer process UI tests.