tests-e2e

Name: tests-e2e
Availability: InStock
Author: ESPlotter

Validate end-to-end user flows across Electron renderer, preload, and main processes.

Updated Aug 27, 2026

Search Tags:#testing #e2e #playwright #electron #ui-testing #test-automation

Ready to run

npx skills add https://github.com/ESPlotter/ESPlotter --skill tests-e2e

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tests-e2e
Source: https://github.com/ESPlotter/ESPlotter/tree/main/.github/skills/tests-e2e
Command: npx skills add https://github.com/ESPlotter/ESPlotter --skill tests-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing for Electron apps is complex and brittle; this skill provides a structured approach to design, implement, and validate robust E2E flows across renderer, preload, and main processes.

Core Features & Use Cases

Standardized Test Object pattern for UI interactions across menus, dialogs, and IPC.
Deterministic test execution with setup/teardown, isolation, and stable waits.
Support for dev vs packaged runtime parity validation and production-like flows.

Quick Start

Run npm run test:e2e to execute the standardized end-to-end tests for Electron app flows.

Frequently Asked Questions about tests-e2e

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

FAQPage Schema

How do I test end-to-end user flows that cross the main and renderer processes in Electron apps?▼

End-to-end user flows in Electron apps are validated by identifying and testing interactions that cross renderer, preload, and main processes. This ensures deterministic execution and stable outcomes across IPC, menus, and persistence layers.

What is the best way to validate test parity between development and packaged Electron runtimes?▼

Test parity between dev and packaged runtimes is validated by enforcing production-like flows and packaging parity checks. This ensures that menus, dialogs, and IPC behave consistently across different runtime environments.

How do I structure UI test automation to avoid brittle selectors and sleeps in Playwright?▼

UI test automation avoids brittle selectors and sleeps by using reusable Test Objects in e2e/support alongside explicit waits. This pattern standardizes interactions and enforces deterministic test execution for stable outcomes.

Does this approach support testing Electron IPC and native dialogs in test automation?▼

Yes, testing Electron IPC and native dialogs is fully supported within the test automation scope. The structured approach validates interactions across menus, dialogs, and inter-process communication for both happy-path and regression scenarios.

Why does my Electron E2E test fail due to flaky execution and missing setup isolation?▼

Electron E2E tests fail flakily when lacking explicit setup and teardown isolation. Deterministic execution is enforced through structured setup/teardown, minimal sleeps, and explicit waits to ensure stable and isolated test outcomes.