windows-qa-engineer

Automate Windows 11 desktop UI testing with UIA accessibility assertions.

119|10|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/CodeAlive-AI/ai-driven-development --skill windows-qa-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-qa-engineer
Source: https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/windows-qa-engineer
Command: npx skills add https://github.com/CodeAlive-AI/ai-driven-development --skill windows-qa-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fastmcp, pydantic, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It eliminates the unreliable “browser-only” or mocked UI testing approach by enabling deterministic QA on real Windows 11 desktop apps using the same physical desktop as the System Under Test (SUT).

Core Features & Use Cases

  • Real Windows UI automation (no mocks): Drives and inspects WinForms/WPF/UWP/Win32 UI via UFO using accessibility trees (UIA by default, Win32 fallback).
  • Fast MCP tool composition: Mounts UFO’s UICollector, HostUIExecutor, and AppUIExecutor into a single stdio MCP server (FastMCP), so the agent only needs one MCP entry.
  • QA-first workflow with assertions: Provides helper tools for discovering windows, re-collecting controls, screenshot baselines, and polling assertions like qa_wait_for_text_contains to avoid arbitrary sleeps.
  • Use cases: Smoke/regression checks for login flows, form input verification, dialog workflows, and desktop UI validation where controls must be discovered reliably from the accessibility tree.

Quick Start

Tell the agent: Test the login flow on MyApp, then provide the window title hint so it can discover the SUT, drive UI controls, assert expected text, and report PASS/FAIL with screenshots.

Frequently Asked Questions about windows-qa-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Windows desktop UI testing without using mocked browsers?

Windows desktop UI testing can be automated on the real SUT by driving WinForms, WPF, UWP, and Win32 applications through UFO-powered accessibility trees. This approach inspects physical UI controls directly, eliminating the need for unreliable browser-only or mocked testing environments.

What is the best way to run smoke and regression tests on Windows 11 desktop apps?

Smoke and regression tests for Windows 11 desktop apps run by discovering windows, driving UI controls, and validating expected text using accessibility backends. Polling assertions like qa_wait_for_text_contains verify UI states reliably without arbitrary sleeps during login flows or dialog workflows.

Does UI automation testing work with WinForms, WPF, and UWP applications?

UI automation testing works with WinForms, WPF, UWP, and Win32 workflows by applying UIA accessibility backends with a Win32 fallback. It drives controls and validates form inputs, navigation steps, and dialog workflows directly from the accessibility tree.

How do I validate expected text in desktop application QA testing?

Expected text in desktop application QA testing is validated using polling assertions like qa_wait_for_text_contains over UIA and Win32 accessibility backends. This method checks UI controls dynamically, avoiding arbitrary sleeps while confirming login forms and dialog text accurately.

Why do I need FastMCP and UFO tools for Windows desktop QA?

FastMCP and UFO tools are needed for Windows desktop QA to mount UICollector, HostUIExecutor, and AppUIExecutor into a single stdio MCP server. This composition provides helper tools for window discovery, control re-collection, and screenshot capture, enabling deterministic testing on the physical desktop.

Can I capture screenshots during automated Windows UI testing workflows?

Screenshots can be captured during automated Windows UI testing workflows using built-in QA helper tools. The agent captures screenshot baselines while driving UI controls and polling assertions, reporting PASS/FAIL outcomes with visual evidence for desktop UI validation.