desktop-e2e

Name: desktop-e2e
Availability: InStock
Author: sbluemin

Automate end-to-end testing of the Fleet Console Electron Desktop shell.

16|2|Updated Mar 17, 2026

Search Tags:#test automation #Electron #end-to-end testing #shell testing #Fleet Console

Ready to run

npx skills add https://github.com/sbluemin/fleet-harness --skill desktop-e2e

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: desktop-e2e
Source: https://github.com/sbluemin/fleet-harness/tree/main/.agents/skills/desktop-e2e
Command: npx skills add https://github.com/sbluemin/fleet-harness --skill desktop-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires electron, playwright, fleet-desktop, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the end-to-end testing of the Fleet Console Electron Desktop shell, streamlining the process of diagnosing and validating the shell's functionality.

Core Features & Use Cases

Automated Testing: Execute headed end-to-end tests for the Fleet Console Electron Desktop shell.
Diagnosis: Collect evidence across renderer, main process, sidecar ownership, native UI, and packaged artifact boundaries.
Use Case: When developing or updating the Fleet Console Electron Desktop shell, use this Skill to ensure that all components are functioning correctly and to catch issues early in the development cycle.

Quick Start

Run the desktop-e2e skill to execute end-to-end tests for the Fleet Console Electron Desktop shell.

Frequently Asked Questions about desktop-e2e

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 shell?▼

Automate end-to-end testing for an Electron desktop shell by running tests across the renderer, main process, and native UI to validate functionality and catch issues early in the development cycle.

What is the best way to test sidecar ownership in a Fleet Console Electron app?▼

Testing sidecar ownership in a Fleet Console Electron app involves collecting diagnostic evidence across main process boundaries and packaged artifacts to ensure correct component handoff.

Does Playwright work for testing native UI and packaged artifact boundaries in Electron?▼

Yes, Playwright supports testing native UI and packaged artifact boundaries in Electron by executing headed end-to-end tests that validate the renderer and main process interactions.

How do I diagnose issues across the main process and renderer in an Electron desktop app?▼

Diagnose issues across the main process and renderer by executing automated end-to-end tests that collect evidence on sidecar ownership, native UI, and packaged artifact boundaries.

Can I run headed end-to-end tests for the Fleet Console Electron Desktop shell?▼

Yes, you can run headed end-to-end tests for the Fleet Console Electron Desktop shell to comprehensively validate the shell's functionality and ensure proper Console handoff.

Do I need Electron and Playwright to test the Fleet Desktop components?▼

Yes, you need Electron and Playwright as dependencies to automate end-to-end testing and validate the Fleet Desktop components, including sidecar ownership and native UI.