Windows Desktop E2e

Automates Windows desktop apps (WPF, WinForms, Win32, Qt) using pywinauto and the built-in UI Automation API. Covers the full E2E stack: page object setup, locators by AutomationId, waits, CI integration, and framework-specific testability guidance. The Qt section alone is worth it if you've ever fought with objectName mapping or accessibility flags across Qt 5.x and 6.x. It assumes you'll use Accessibility Insights to inspect the UIA tree before writing selectors, which is the right call. If your app has stable AutomationIds this will save you days of flaky text-matching hacks. Skip it for Electron or web apps, those need Playwright.

skills.sh installs: 5.7K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill windows-desktop-e2e --agent claude-code

Installs into .claude/skills of the current project.

Files

Windows Desktop E2E Testing

End-to-end testing for Windows native desktop applications using pywinauto backed by Windows UI Automation (UIA). Covers WPF, WinForms, Win32/MFC, and Qt (5.x / 6.x) — with Qt-specific guidance as a dedicated section.

When to Activate

Writing or running E2E tests for a Windows native desktop application
Setting up a desktop GUI test suite from scratch
Diagnosing flaky or failing desktop automation tests
Adding testability (AutomationId, accessible names) to an existing app
Integrating desktop E2E into a CI/CD pipeline (GitHub Actions windows-latest)

When NOT to Use

Web applications → use e2e-testing skill (Playwright)
Electron / CEF / WebView2 apps → the HTML layer needs browser automation, not UIA
Mobile apps → use platform-specific tools (UIAutomator, XCUITest)
Pure unit or integration tests that don't need a running GUI

Core Concepts

All Windows desktop automation relies on UI Automation (UIA), a Windows-built-in accessibility API. Every supported framework exposes a tree of UIA elements with properties Claude can read and act on:

SKILL.md on GitHub