Windows Desktop E2E Testing
End-to-end testing for Windows desktop apps (WPF, WinForms, Qt) with pywinauto and UI Automation: locators, page objects, waits, flaky-test triage, and CI setup.
- What
- End-to-end testing for Windows desktop apps (WPF, WinForms, Qt) with pywinauto and UI Automation: locators, page objects, waits, flaky-test triage, and CI setup.
- Cost
- Free
- Needs
- Use "Windows Desktop E2E Testing" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: end-to-end testing for Windows native desktop applications using pywinauto backed by Windows UI Automation. Covers WPF, WinForms, Win32/MFC, and Qt 5.x/6.x, with a UIA quality table per framework so you know what to expect before writing a line. The core discipline: give every interactive control a stable AutomationId first (x:Name in WPF, AccessibleName in WinForms, objectName in Qt), then locate by AutomationId, never by pixel coordinates. Ships a complete pytest suite layout: Page Object Model with a BasePage (locators, explicit waits, screenshot helpers), app-launch fixtures with failure screenshots, config via environment variables, and pytest.ini ready for CI. Goes deep on the hard parts: wait patterns that replace time.sleep, artifact management (screenshots, ffmpeg screen recording, opt-in per-step JSONL traces with PII redaction), flaky test triage with a cause-to-fix table, three tiers of test isolation (filesystem redirect, Windows Job Objects, full Windows Sandbox), and a GitHub Actions workflow for windows-latest runners. Qt gets its own section: enabling UIA in Qt 5.x, stable test IDs, QComboBox and QDialog quirks, plus a screenshot-mode fallback with OpenCV template matching for self-drawn controls. Use when writing or running E2E tests for a Windows desktop app, setting up a GUI suite from scratch, or diagnosing flaky desktop automation. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: Windows only, Python 3.8+; UIA reliability varies by framework (Win32/MFC is fair, not excellent); screenshot fallback is fragile against DPI and theme changes, always try UIA first. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Windows Desktop E2E Testing" with your Muse. Prerequisites: Windows with Python 3.8+, and the desktop app you want to test. Install: pip install pywinauto pytest pytest-html Pillow. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/windows-desktop-e2e/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Set up (or debug) E2E tests for my Windows app: [framework, e.g. WPF, and what to test]." 3. Ask it to start with testability: stable AutomationIds on every control, then the Page Object layout. Tip: use Accessibility Insights for Windows to inspect the UIA tree before writing locators. Safety: a skill is plain-text instructions; it runs nothing by itself. Never enable per-step trace text capture on login or payment flows.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.