windows-desktop-e2e

Topics in the source

• Windows Desktop E2E Testing
• When to Activate
• When NOT to Use
• Core Concepts
• Setup & Prerequisites
• Testability Setup (by Framework)
• WPF
• WinForms

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. 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) 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 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: UIA quality by framework: | Framework | AutomationId | Reliability | Notes | |-----------|-------------|-------------|-------| | WPF | 5/5 | Excellent | x:Name maps directly to AutomationId | | Win

This is an excerpt. Refer to the complete source and its current requirements.