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
- a Windows machine — this skill drives Windows UI Automation and cannot run on macOS or Linux; Python 3.8+ on that Windows machine; and the Windows desktop app I want to test. The Python packages the skill prescribes (pywinauto, pytest, pytest-html, Pillow, pytest-timeout) are installed on Windows into a virtual environment (`python -m venv .venv`, then the environment's pip), because a bare `pip install` is refused on externally managed Python (PEP 668). No account and no API key are needed.
- Level
- Intermediate — a Windows machine…
- 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:
Quick answer
Windows Desktop E2E Testing is a free skill for Muse. 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.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Windows machine — this skill drives Windows UI Automation and cannot run on macOS or Linux; Python 3.8+ on that Windows machine; and the Windows desktop app I want to test. The Python packages the skill prescribes (pywinauto, pytest, pytest-html, Pillow, pytest-timeout) are installed on Windows into a virtual environment (`python -m venv .venv`, then the environment's pip), because a bare `pip install` is refused on externally managed Python (PEP 668). No account and no API key are needed. Install "Windows Desktop E2E Testing" for me. It gives my agent end-to-end testing guidance for Windows native desktop apps (WPF, WinForms, Win32/MFC, and Qt) using pywinauto backed by the Windows UI Automation API: testability setup with stable AutomationIds, a page object layout, and diagnosis of flaky desktop tests. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/windows-desktop-e2e/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprint below. I want you to compute the SHA-256 of the downloaded file and compare: - SKILL.md: SHA-256 cbc93a1e2514ecdcee30da744aa13eb6c0ebe4948ca3dfff52b287df4f9f0814 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none — this is a plain Markdown guidance file and it contacts nothing by itself) - every shell command it runs (expected: none during installation; the file describes Python test code and commands my agent writes and runs later, on Windows, when the skill is used) - every place credentials, API keys or personal data are read, stored or sent (expected: none; the file also warns never to enable per-step trace text capture on login or payment flows) - any obfuscated or encoded code (expected: none — plain Markdown text) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "windows-desktop-e2e". 6. Verify with no network calls: frontmatter valid, files in place. 7. Report what was installed, where, and what I still need to do myself (for example: on my Windows machine, create the virtual environment and install the prescribed packages into it, and install Accessibility Insights for Windows to inspect the UI Automation tree before writing locators). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can run commands on your Muse’s computer.
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- runs commands — Prerequisites: a Windows machine — this skill drives Windows UI Automation and cannot run on macOS or Linux; P · - chaque commande shell qu'il exécute (attendu : aucune pendant l'installation ; le fichier décrit du code de
- installs packages — Prerequisites: a Windows machine — this skill drives Windows UI Automation and cannot run on macOS or Linux; P · Prérequis : une machine Windows — ce skill pilote Windows UI Automation et ne peut pas fonctionner sous macOS
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : runs commands · installs packages
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.